Uplink Transmission Cancellation in Non-Terrestrial Networks

ABSTRACT

A wireless device receives a first downlink control information (DCI) that schedules a reception of a transport block and indicates a hybrid automatic request (HARQ) process number with feedback disabled. The wireless device receives a second DCI that schedules a retransmission of the transport block and indicates the HARQ process number with feedback disabled, where the retransmission of the transport block overlaps in time with at least one symbol of a transmission of an uplink signal. Based on successfully decoding the transport block scheduled by the first DCI, the wireless device drops the retransmission of the transport block scheduled by the second DCI and transmits the uplink signal.

CROSS-REFERENCE T0 RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 63/229,648, filed Aug. 5, 2021, which is hereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with two component carriers.

FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure and location.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communication with a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.

FIG. 17 shows several examples of DCI formats.

FIG. 18 shows example PDSCH processing times.

FIG. 19 shows examples of PUSCH preparation/processing time.

FIG. 20A shows an example of a wireless device without partialCancellation capability transmitting an uplink channel/signal.

FIG. 20B shows an example of a wireless device without partialCancellation capability transmitting an UL channel/signal.

FIG. 21A shows an example of a wireless device with partialCancellation capability transmitting an UL channel/signal.

FIG. 21B shows an example of a wireless device transmitting an SRS.

FIG. 22 is an example figure of different types of NTN platforms/nodes.

FIG. 23 shown an example of an NTN with a transparent NTN platform/node.

FIG. 24 shows examples of propagation delay corresponding to NTNs of different altitudes.

FIG. 25 shows an example of downlink communication between a base station and a wireless device in an NTN scenario with a feedback disabled HARQ process.

FIG. 26 shows an example of downlink data transmission with a feedback disabled HARQ process between a base station and a wireless device in an NTN scenario.

FIG. 27 shows an example embodiment of a wireless device communicating with an NTN base station, in accordance with certain aspects of the present disclosure.

FIG. 28 shows an example embodiment of a wireless device with partialCancellation capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure.

FIG. 29 shows an example embodiment of a wireless device with partialCancellation capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure.

FIG. 30 shows an example embodiment of a wireless device without partialCancellation capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure.

FIG. 31 shows an example embodiment of a wireless device capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure.

FIG. 32 shows an example embodiment of a wireless device capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure.

FIG. 33 shows an example embodiment of a wireless device communicating with an NTN base station, in accordance with certain aspects of the present disclosure.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and/or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and/or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of”, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, should be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and/or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B ={cell1, ce112} are: {cell1}, {ce112}, and {cell1, ce112}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing/using” (or equally “employing/using at least”) is indicative that the phrase following the phrase “employing/using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, or Information elements: IEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.

Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

1. Network Architecture

FIG. 1A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs. As part of the interface functionality, the CN 102 may set up end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 through radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 over the air interface is known as the downlink and the communication direction from the wireless device 106 to the RAN 104 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time-division duplexing (TDD), and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device may be a telephone, smart phone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle road side unit (RSU), relay node, automobile, and/or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and/or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and/or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB, associated with NR and/or 5G standards), an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard), and/or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to respectively control three cells (or sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility.

In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectored site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and/or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same/similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.

The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 in FIG. 1A. To date, 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as next-generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. Mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG. 1B, mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other network functions. The network functions of the 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF/UPF 158 in FIG. 1B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink/downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra-/inter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and/or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks,_idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policies), network slicing support, and/or session management function (SMF) selection. NAS may refer to the functionality operating between a CN and a UE, and AS may refer to the functionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more gNB s, illustrated as gNB 160A and gNB 160B (collectively gNBs 160) and/or one or more ng-eNB s, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNB s 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNB s 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and/or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and/or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNB s 160 and/or the ng-eNB s 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNB s 162 may be connected to one or more AMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations toward the UE 156A over a Uu interface associated with a first protocol stack. The ng-eNBs 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs 156 over a Uu interface, where E-UTRA refers to the 3GPP 4G radio-access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may be connected to multiple AMF/UPF nodes to provide redundancy and/or to load share across the multiple AMF/UPF nodes.

2. Radio Protocol Architecture

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1B may be associated with a protocol stack that the network elements use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220. The protocol stacks illustrated in FIG. 2A and FIG. 2B may be the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. 1B.

2.1 User Plane Protocol Stack

FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise media access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3 , the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and/or error rate). The SDAPs 215 and 225 may perform mapping/de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping/de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering/deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-gNB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

Although not shown in FIG. 3 , PDCPs 214 and 224 may perform mapping/de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity. The PDCPs 214 and 224 may map/de-map the split radio bearer between RLC channels belonging to cell groups.

The RLCs 213 and 223 may perform segmentation, retransmission through

Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and/or Transmission Time Interval (TTI) durations. As shown in FIG. 3 , the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logical channels and/or mapping between logical channels and transport channels. The multiplexing/demultiplexing may include multiplexing/demultiplexing of data units, belonging to the one or more logical channels, into/from Transport Blocks (TBs) delivered to/from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and/or padding. The MACs 212 and 222 may support one or more numerologies and/or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and/or transmission timing a logical channel may use. As shown in FIG. 3 , the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding/decoding and modulation/demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3 , the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.

FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TB s at the gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IP packet. The data unit from/to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to/from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown in FIG. 4A, the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associated functionality (e.g., with respect to FIG. 3 ), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to the MAC 222. The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel_identifier (LCID) field for_identifying the logical channel from which the MAC SDU originated to aid in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation/deactivation MAC CEs, such as those for activation/deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be_identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR include, for example:

-   -   a paging control channel (PCCH) for carrying paging messages         used to page a UE whose location is not known to the network on         a cell level;     -   a broadcast control channel (BCCH) for carrying system         information messages in the form of a master information block         (MIB) and several system information blocks (SIBs), wherein the         system information messages may be used by the UEs to obtain         information about how a cell is configured and how to operate         within the cell;     -   a common control channel (CCCH) for carrying control messages         together with random access;     -   a dedicated control channel (DCCH) for carrying control messages         to/from a specific the UE to configure the UE; and     -   a dedicated traffic channel (DTCH) for carrying user data         to/from a specific the UE.

Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR include, for example:

-   -   a paging channel (PCH) for carrying paging messages that         originated from the PCCH;     -   a broadcast channel (BCH) for carrying the MIB from the BCCH;     -   a downlink shared channel (DL-SCH) for carrying downlink data         and signaling messages, including the SIBs from the BCCH;     -   an uplink shared channel (UL-SCH) for carrying uplink data and         signaling messages; and     -   a random access channel (RACH) for allowing a UE to contact the         network without any prior scheduling.

The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1/L2 control channels. The set of physical channels and physical control channels defined by NR include, for example:

-   -   a physical broadcast channel (PBCH) for carrying the MIB from         the BCH;     -   a physical downlink shared channel (PDSCH) for carrying downlink         data and signaling messages from the DL-SCH, as well as paging         messages from the PCH;     -   a physical downlink control channel (PDCCH) for carrying         downlink control information (DCI), which may include downlink         scheduling commands, uplink scheduling grants, and uplink power         control commands;     -   a physical uplink shared channel (PUSCH) for carrying uplink         data and signaling messages from the UL-SCH and in some         instances uplink control information (UCI) as described below;     -   a physical uplink control channel (PUCCH) for carrying UCI,         which may include HARQ acknowledgments, channel quality         indicators (CQI), pre-coding matrix indicators (PMI), rank         indicators (RI), and scheduling requests (SR); and     -   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG. 5A and FIG. 5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.

2.2 Control Plane Protocol Stack

FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same/similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221, the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead of having the SDAPs 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which the NAS messages can be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same/similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control-plane and user-plane data into the same transport block (TB). The RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and/or NAS message transfer. As part of establishing an RRC connection, RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. The UE may be the same or similar to the wireless device 106 depicted in FIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any other wireless device described in the present disclosure. As illustrated in FIG. 6 , a UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC_idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session); security information; and/or PHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC_idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.

In RRC_idle 604, an RRC context may not be established for the UE. In RRC_idle 604, the UE may not have an RRC connection with the base station. While in RRC_idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC_idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established is maintained in the UE and the base station. This allows for a fast transition to RRC connected 602 with reduced signaling overhead as compared to the transition from RRC_idle 604 to RRC connected 602. While in RRC inactive 606, the UE may be in a sleep state and mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive 606 to RRC connected 602 through a connection resume procedure 614 or to RRC idle 604 though a connection release procedure 616 that may be the same as or similar to connection release procedure 608.

An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC_idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC_idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC_idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area_identified by a RAN area_identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and_identified by a tracking area_identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN (e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be assigned a RAN notification area. A RAN notification area may comprise one or more cell_identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE's RAN notification area.

A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and/or during a period of time that the UE stays in RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an Fl interface. The gNB-CU may comprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

3. Transmission Structure

In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped. An NR frame may be_identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As illustrated, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerologies with the following subcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3 μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration). A subframe in NR may be used as a numerology-independent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8 . An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8 . An NR carrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

4. Transmission and Reception Techniques 4.1 Bandwidth Parts

NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and/or for other purposes, a UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell may be active. These one or more BWPs may be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink Control Information

(DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

A base station may semi-statically configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide the default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value for a PCell.

The UE may start or restart a BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and/or in response to an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a not currently active BWP) may be performed independently in paired spectra. In unpaired spectra, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and/or an initiation of random access.

FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9 , the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9 , the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and/or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and/or in response receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response receiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell may be the same/similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same/similar manner as the UE would use these values for a primary cell.

4.2 Carrier Aggregation

To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to/from the same UE using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CCs). When CA is used, there are a number of serving cells for the UE, one for a CC. The CCs may have three configurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In the intraband, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and/or duplexing schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may be optionally configured for a serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and/or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells may be activated and deactivated using a MAC CE with respect to FIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as self-scheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and/or RI) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary Scell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, and UCI 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index. The physical cell ID or the cell index may identify a downlink carrier and/or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. A cell index may be determined using RRC messages. In the disclosure, a physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same/similar concept may apply to, for example, a carrier activation. When the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In an example, a HARQ entity may operate on a serving cell. A transport block may be generated per assignment/grant per serving cell. A transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.

5. Reference Signals

In the downlink, a base station may transmit (e.g., unicast, multicast, and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and the SSS may be provided in a synchronization signal (SS)/physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH. The base station may periodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block's structure and location. A burst of SS/PBCH blocks may include one or more SS/PBCH blocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG. 11A is an example, and that these parameters (number of SS/PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS/PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS/PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, the SSS, and the PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell). To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS/PBCH block, the locations of the SSS and the PBCH, respectively. The SS/PBCH block may be a cell-defining SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, a cell selection/search and/or reselection may be based on the CD-SSB.

The SS/PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell_identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS/PBCH block. For example, the SS/PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS/PBCH block in the transmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and/or a SS/PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB 1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may be pointed to a frequency. The UE may search for an SS/PBCH block at the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with a same SS/PBCH block index are quasi co-located (QCLed) (e.g., having the same/similar Doppler spread, Doppler shift, average gain, average delay, and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCH block transmissions having different SS/PBCH block indices.

SS/PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell). In an example, a first SS/PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS/PBCH block may be transmitted in a second spatial direction using a second beam.

In an example, within a frequency span of a carrier, a base station may transmit a plurality of SS/PBCH blocks. In an example, a first PCI of a first SS/PBCH block of the plurality of SS/PBCH blocks may be different from a second PCI of a second SS/PBCH block of the plurality of SS/PBCH blocks. The PCIs of SS/PBCH blocks transmitted in different frequency locations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a UE with one or more of the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs. The UE may estimate a downlink channel state and/or generate a CSI report based on the measuring of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

The base station may semi-statically configure the UE with one or more CSI-RS resource sets. A CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity. The base station may selectively activate and/or deactivate a CSI-RS resource. The base station may indicate to the UE that a CSI-RS resource in the CSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and/or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and/or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure the UE with a number (e.g. a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MIMO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. A radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence may be the same or different. The base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRSs for coherent demodulation/channel estimation of the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and/or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and/or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS. An NR network may support a plurality of PT-RS densities defined in the time and/or frequency domains. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time/frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and/or a PUCCH. The base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and/or the PUCCH, which the UE may use to schedule a single-symbol DMRS and/or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence for the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase tracking and/or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and/or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and/or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and/or link adaptation. SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies. A scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, an SRS resource in a SRS resource set of the one or more SRS resource sets (e.g., with the same/similar time domain behavior, periodic, aperiodic, and/or the like) may be transmitted at a time instant (e.g., simultaneously). The UE may transmit one or more SRS resources in SRS resource sets. An NR network may support aperiodic, periodic and/or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats. In an example, at least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.

The base station may semi-statically configure the UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier; a number of SRS ports; time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/or subframe level periodicity; offset for a periodic and/or an aperiodic SRS resource; a number of OFDM symbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and/or an SRS sequence ID.

6. Beamforming

An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and/or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi co-located (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and/or spatial Receiving (Rx) parameters.

Channels that use beamforming require beam management. Beam management may comprise beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be_identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on downlink reference signals (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform the downlink beam measurement procedure after an RRC connection is set up with a base station.

FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and/or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration_identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resource parameters.

The three beams illustrated in FIG. 11B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11B (beam #1, beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and/or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam_identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam management procedures: P1, P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and/or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). The UE and/or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam management procedures: U1, U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and/or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and/or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, a UCI, an SR, a MAC CE, and/or the like) based on the initiating of the BFR procedure. The UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and/or the like).

The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS/PBCH blocks, one or more CSI-RS resources, and/or one or more demodulation reference signals (DMRSs). A quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and/or a CSI value measured on RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and/or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and/or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.

7. Random Access

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE may initiate a random access procedure. A UE in an RRC_IDLE state and/or an RRC_INACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and/or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and/or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and/or for establishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 may include and/or be referred to as a preamble (or a random access preamble). The Msg 2 1312 may include and/or be referred to as a random access response (RAR).

The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and/or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and/or in an RRC_INACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and/or an uplink transmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 4 1314.

The one or more RACH parameters provided in the configuration message 1310 may indicate one or more Physical RACH (PRACH) occasions available for transmission of the Msg 1 1311. The one or more PRACH occasions may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-Configlndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS/PBCH blocks and/or CSI-RSs. For example, the one or more RACH parameters may indicate a number of SS/PBCH blocks mapped to a PRACH occasion and/or a number of preambles mapped to a SS/PBCH blocks.

The one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 1 1311 and/or Msg 3 1313. For example, the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and/or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 1 1311 and the Msg 3 1313; and/or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., an SSB and/or CSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and/or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and/or a size of the Msg 3 1313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and/or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and/or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and/or a size of the Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and/or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and/or CSI-RSs). If the association is configured, the UE may determine the preamble to include in Msg 1 1311 based on the association. The Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and/or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMsklndex and/or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.

The UE may perform a preamble retransmission if no response is received following a preamble transmission. The UE may increase an uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a pathloss measurement and/or a target received preamble power configured by the network. The UE may determine to retransmit a preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_ RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and/or CSI-RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and/or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs. The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE's transmission timing, a scheduling grant for transmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Typel-PDCCH common search space) configured by an RRC message. The UE may_identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and/or a UL carrier indicator of the PRACH occasions.An example of RA-RNTI may be as follows:

RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id where s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0≤s_id<14), t_id may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0≤t_id<80), f_id may be an index of the PRACH occasion in the frequency domain (e.g., 0≤f_id<8), and ul_carrier_id may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 2 1312 (e.g., using resources_identified in the Msg 2 1312). The Msg 3 1313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 3 1313 and the Msg 4 1314) may be used to increase the likelihood that the UE does not incorrectly use an_identity of another the UE. To perform contention resolution, the UE may include a device_identifier in the Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and/or any other suitable_identifier).

The Msg 4 1314 may be received after or in response to the transmitting of the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 4 1314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that the contention resolution is successful and/or the UE may determine that the random access procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases. For example, the UE may determine and/or switch an uplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on a channel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG. 13A, a base station may, prior to initiation of the procedure, transmit a configuration message 1320 to the UE. The configuration message 1320 may be analogous in some respects to the configuration message 1310. The procedure illustrated in FIG. 13B comprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322. The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention-free random access procedure may not include messages analogous to the Msg 3 1313 and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B may be initiated for a beam failure recovery, other SI request, SCell addition, and/or handover. For example, a base station may indicate or assign to the UE the preamble to be used for the Msg 1 1321. The UE may receive, from the base station via PDCCH and/or RRC, an indication of a preamble (e.g., ra-Preamblelndex).

After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and/or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceId). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure illustrated in FIG. 13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 2 1322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble_identifier corresponding to a preamble transmitted by the UE and/or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request.

FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 may be analogous in some respects to the configuration message 1310 and/or the configuration message 1320. The procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and/or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and/or equivalent to the contents of the Msg 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated in FIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C for licensed spectrum and/or unlicensed spectrum. The UE may determine, based on one or more factors, whether to initiate the two-step random access procedure. The one or more factors may be: a radio access technology in use (e.g., LTE, NR, and/or the like); whether the UE has valid TA or not; a cell size; the UE's RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in the configuration message 1330, a radio resource and/or an uplink transmit power for the preamble 1341 and/or the transport block 1342 included in the Msg A 1331. The RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and/or a power control for the preamble 1341 and/or the transport block 1342. A time-frequency resource for transmission of the preamble 1341 (e.g., a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and/or receiving Msg B 1332.

The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and/or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit the Msg B 1332 as a response to the Msg A 1331. The Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and/or an MCS); a UE identifier for contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if: a preamble identifier in the Msg B 1332 is matched to a preamble transmitted by the UE; and/or the identifier of the UE in Msg B 1332 is matched to the_identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).

8. Physical-Layer Control Signaling

A UE and a base station may exchange control signaling. The control signaling may be referred to as L1/L2 control signaling and may originate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g., layer 2). The control signaling may comprise downlink control signaling transmitted from the base station to the UE and/or uplink control signaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and/or a transport format; a slot format information; a preemption indication; a power control command; and/or any other suitable signaling. The UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of the UEs), the base station may scramble the CRC parity bits with an_identifier of the UE (or an_identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the_identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and/or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and/or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and/or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling and/or QPSK modulation. A base station may map the coded and modulated DCI on resource elements used and/or configured for a PDCCH. Based on a payload size of the DCI and/or a coverage of the base station, the base station may transmit the DCI via a PDCCH occupying a number of contiguous control channel elements (CCEs). The number of the contiguous CCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/or any other suitable number. A CCE may comprise a number (e.g., 6) of resource-element groups (REGs). A REG may comprise a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a time-frequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs at a third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and/or frequency-selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and/or whether a search space set is a common search space set or a UE-specific search space set. A set of CCEs in the common search space set may be predefined and known to the UE. A set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource for a CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and/or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and/or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL-SCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message. The plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being_identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to “1”. If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.

9. Base Station and UE Implementation

FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15 , but it will be understood that a mobile communication network may include more than one UE and/or more than one base station, with the same or similar configuration as those shown in FIG. 15 .

The base station 1504 may connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and/or some combination of the two duplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent to the base station 1504 from the wireless device 1502 may be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A. Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent to the wireless device 1502 may be provided to a transmission processing system 1510 of base station 1504. Similarly, after being processed by the processing system 1518, the data to be sent to base station 1504 may be provided to a transmission processing system 1520 of the wireless device 1502. The transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 may receive the downlink transmission from base station 1504. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and/or the like.

As shown in FIG. 15 , a wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit/receive diversity, and/or beamforming. In other examples, the wireless device 1502 and/or the base station 1504 may have a single antenna.

The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and/or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG. 15 , the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and/or the reception processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.

The processing system 1508 and/or the processing system 1518 may comprise one or more controllers and/or one or more processors. The one or more controllers and/or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and/or other programmable logic device, discrete gate and/or transistor logic, discrete hardware components, an on-board unit, or any combination thereof. The processing system 1508 and/or the processing system 1518 may perform at least one of signal coding/processing, data processing, power control, input/output processing, and/or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

The processing system 1508 and/or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and/or hardware that provide features and/or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and/or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and/or the like). The processing system 1508 and/or the processing system 1518 may receive user input data from and/or provide user output data to the one or more peripherals 1516 and/or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and/or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and/or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, an CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.

FIG. 16C illustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for an antenna port; and/or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages (e.g. RRC messages) comprising configuration parameters of a plurality of cells (e.g. primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g. two or more base stations in dual-connectivity) via the plurality of cells. The one or more messages (e.g. as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g. the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period/window for a process. When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period/window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

A base station may transmit one or more MAC PDUs to a wireless device. In an example, a MAC PDU may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, bit strings may be represented by tables in which the most significant bit is the leftmost bit of the first line of the table, and the least significant bit is the rightmost bit on the last line of the table. More generally, the bit string may be read from left to right and then in the reading order of the lines. In an example, the bit order of a parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit. In an example, a MAC SDU may be included in a MAC PDU from the first bit onward. A MAC control element (CE) may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. A MAC subheader may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, a MAC subheader may be placed immediately in front of a corresponding MAC SDU, MAC CE, or padding.

In an example, a MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the one or more MAC subPDUs may comprise: a MAC subheader only (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; a MAC subheader and padding, or a combination thereof. The MAC SDU may be of variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

In an example, when a MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may comprise: a Reserve field (R fieId) with a one bit length; an Format filed (F fieId) with a one-bit length; a Logical Channel Identifier (LCID) field with a multi-bit length; a Length field (L fieId) with a multi-bit length, indicating the length of the corresponding MAC SDU or variable-size MAC CE in bytes, or a combination thereof. In an example, F field may indicate the size of the L field.

In an example, a MAC entity of a base station may transmit one or more MAC CEs to a MAC entity of a wireless device. The one or more MAC CEs may comprise at least one of: a SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE, a PUCCH spatial relation Activation/Deactivation MAC CE, a SP SRS Activation/Deactivation MAC CE, a SP CSI reporting on PUCCH Activation/Deactivation MAC CE, a TCI State Indication for UE-specific PDCCH MAC CE, a TCI State Indication for UE-specific PDSCH MAC CE, an Aperiodic CSI Trigger State Subselection MAC CE, a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE, a UE contention resolution identity MAC CE, a timing advance command MAC CE, a DRX command MAC CE, a Long DRX command MAC CE, a secondary cell (SCell) activation/deactivation MAC CE (1 Octet), an SCell activation/deactivation MAC CE (4 Octet), and/or a duplication activation/deactivation MAC CE. In an example, a MAC CE, such as a MAC CE transmitted by a MAC entity of a base station to a MAC entity of a wireless device, may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CE may have different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a long DRX command MAC CE.

In an example, the MAC entity of the wireless device may transmit to the MAC entity of the base station one or more MAC CEs. The one or more MAC CEs may comprise at least one of: a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single entry PHR MAC CE, a multiple entry PHR MAC CE, a short truncated BSR, and/or a long truncated BSR. In an example, a MAC CE may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CE may have different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a short-truncated command MAC CE.

In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A wireless device may simultaneously receive or transmit on one or more CCs, depending on capabilities of the wireless device, using the technique of CA. In an example, a wireless device may support CA for contiguous CCs and/or for non-contiguous CCs. CCs may be organized into cells. For example, CCs may be organized into one primary cell (PCell) and one or more SCells. When configured with CA, a wireless device may have one RRC connection with a network. In an example, a base station may transmit, to a wireless device, one or more messages comprising configuration parameters of a plurality of one or more SCells, depending on capabilities of the wireless device. When configured with CA, a base station and/or a wireless device may employ an activation/deactivation mechanism of an SCell to improve battery or power consumption of the wireless device. When a wireless device is configured with one or more SCells, a base station may activate or deactivate at least one of the one or more SCells. Upon configuration of an SCell, the SCell may be deactivated unless an SCell state associated with the SCell is set to “activated” or “dormant.” A wireless device may activate/deactivate an SCell in response to receiving an SCell Activation/Deactivation MAC CE.

A base station may configure a wireless device with uplink (UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidth adaptation (BA) on a PCell. If carrier aggregation is configured, the base station may further configure the wireless device with at least DL BWP(s) (i.e., there may be no UL BWPs in the UL) to enable BA on an SCell. For the PCell, an initial active BWP may be a first BWP used for initial access. In paired spectrum (e.g., FDD), a base station and/or a wireless device may independently switch a DL BWP and an UL BWP. In unpaired spectrum (e.g., TDD), a base station and/or a wireless device may simultaneously switch a DL BWP and an UL BWP.

In an example, a base station and/or a wireless device may switch a BWP between configured BWPs by means of a DCI or a BWP invalidity timer. When the BWP invalidity timer is configured for a serving cell, the base station and/or the wireless device may switch an active BWP to a default BWP in response to an expiry of the BWP invalidity timer associated with the serving cell. The default BWP may be configured by the network. In an example, for FDD systems, when configured with BA, one UL BWP for each uplink carrier and one DL BWP may be active at a time in an active serving cell. In an example, for TDD systems, one DL/UL BWP pair may be active at a time in an active serving cell. Operating on the one UL BWP and the one DL BWP (or the one DL/UL pair) may improve wireless device battery consumption. BWPs other than the one active UL BWP and the one active DL BWP that the wireless device may work on may be deactivated. On deactivated BWPs, the wireless device may: not monitor PDCCH; and/or not transmit on PUCCH, PRACH, and UL-SCH. In an example, a MAC entity may apply normal operations on an active BWP for an activated serving cell configured with a BWP comprising: transmitting on UL-SCH; transmitting on RACH; monitoring a PDCCH; transmitting PUCCH; receiving DL-SCH; and/or (re-)initializing any suspended configured uplink grants of configured grant Type 1 according to a stored configuration, if any. In an example, on an inactive BWP for each activated serving cell configured with a BWP, a MAC entity may: not transmit on UL-SCH; not transmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmit SRS, not receive DL-SCH; clear any configured downlink assignment and configured uplink grant of configured grant Type 2; and/or suspend any configured uplink grant of configured Type 1.

In an example, a set of PDCCH candidates for a wireless device to monitor is defined in terms of PDCCH search space sets. A search space set comprises a common search space

(CSS) set or a user search space (USS) set. A wireless device monitors PDCCH candidates in one or more of the following search spaces sets: a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB or by searchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG, a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG, a Typel-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a RA-RNTI, a MSGB-RNTI, or a TC-RNTI on the primary cell, a Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI on the primary cell of the MCG, a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType =common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI(s), and a USS set configured by SearchSpace in PDCCH-Config with searchSpaceType =ue-Specific for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI(s), SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.

In an example, a wireless device may monitor a set of PDCCH candidates according to configuration parameters of a search space set comprising a plurality of search spaces (SSs). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common SSs, and/or number of PDCCH candidates in the UE-specific SSs) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding.

FIG. 17 shows several examples of DCI formats. In an example, several DCI formats may be used by a base station to transmit control information to a wireless device or used by the wireless device for PDCCH monitoring. Different DCI formats may comprise different DCI fields and/or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In an example, DCI format 0_0 may be used to schedule PUSCH in one cell. DCI format 0_1 may be used to schedule one or multiple PUSCH in one cell or indicate CG-DFI (configured grant-Downlink Feedback Information) for configured grant PUSCH, etc. If in an active DL BWP a wireless device monitors PDCCH either for detection of DCI format 0_1 and DCI format 1_1 or for detection of DCI format 0_2 and DCI format 1_2, a priority index can be provided by a priority indicator field. In an example, if a wireless device indicates a capability to monitor, in an active UL BWP, PDCCH for detection of DCI format 0_1 and DCI format 1_1 and for detection of DCI format 0_2 and DCI format 1_2, a DCI format 0_1 or a DCI format 0_2 may schedule a PUSCH transmission of any priority, a DCI format 1_1 or a DCI format 1_2 may schedule a PDSCH reception. According to an example, the DCI format 1_1 or the DCI format 1_2 may trigger a PUCCH transmission with corresponding HARQ-ACK information of any priority. In an example, the DCI format 1_1 may trigger a PUCCH transmission with corresponding HARQ-ACK information of any priority.

In an example, a wireless device may assume that flexible symbols in a CORESET configured to the wireless device for PDCCH monitoring are downlink symbols if the wireless device does not detect an SFI-index field value in a DCI (e.g., DCI format 2_0) indicating one or more symbols of a slot as flexible or uplink and the wireless device does not detect a DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, or DCI format 2_3) indicating to the wireless device to transmit SRS, PUSCH, PUCCH, or PRACH in the one or more symbols.

A wireless technology may use an asynchronous HARQ protocol in the downlink and/or uplink, e.g., the HARQ process which the downlink and/or uplink transmission relates to, may be explicitly and/or implicitly signaled. For example, a DCI scheduling a downlink transmission (or downlink assignment, or downlink signal, or downlink channel) may indicate the corresponding HARQ process. Asynchronous HARQ operation may allow dynamic TDD operation. In an example, the downlink transmission may contain necessary HARQ-related control signaling, e.g., HARQ process number/id; new-data indicator (NDI); code block group (CBG) transmit indicator (CBGTI) and CBG flush indicator (CB_GFI) in case per-CBG retransmission is configured; and/or information to schedule the transmission of the acknowledgment (ACK/NACK) in an uplink (e.g., a PUCCH), such as timing and resource indication information. In an example, a wireless device may provide feedback on success (e.g., an ACK) or failure (e.g., a NACK) of the downlink transmission/assignment (e.g., a PDSCH) to a base station for each scheduled/candidate transport block (TB). HARQ information for DL-SCH, for UL-SCH, or for side link shared channel (SL-SCH) transmissions may consist of NDI, Transport Block size (TBS), Redundancy Version (RV), and HARQ process ID. In an example, one or more downlink assignments received on PDCCH may indicate that there is a transmission on a DL-SCH for a particular MAC entity and provide the relevant HARQ information.

In an example, for downlink, a maximum number of HARQ processes per cell may be supported by a wireless device (e.g., 16 or 32). The number of processes the wireless device may use for the downlink is configured to the wireless device for each cell separately by higher layer parameter nrofHARQ-ProcessesForPDSCH, and when no configuration is provided the wireless device may assume a default number processes (e.g., 8). For uplink, a maximum number of HARQ processes per cell (e.g., 16) may be supported by the wireless device.

A wireless device upon detection of a PDCCH with a DCI format 1_0, 1_1 or 1_2 may attempt to decode the corresponding PDSCHs as indicated by the DCI. In an example, for a first HARQ process ID in a scheduled cell, the wireless device may not receive a first PDSCH that overlaps in time with a second PDSCH. The wireless device may not receive the second PDSCH for the first HARQ process until after the end of the expected transmission of HARQ-ACK corresponding to the first PDSCH. In an example, in the scheduled cell, the wireless device may not receive a first PDSCH and a second PDSCH, starting later than the first PDSCH, with its corresponding HARQ-ACK assigned to be transmitted on a resource ending before the start of a different resource for the HARQ-ACK assigned to be transmitted for the first PDSCH, where the two resources are in different slots for the associated/corresponding HARQ-ACK transmissions. In an example, each slot is composed of a number of symbols indicated by subslotLengthForPUCCH if provided, and the HARQ-ACK for the two PDSCHs are associated with the HARQ-ACK codebook of the same priority. According to an example, in the scheduled cell, the wireless device may not receive a first PDSCH, and a second PDSCH, starting later than the first PDSCH, with its corresponding HARQ-ACK assigned to be transmitted on a resource ending before the start of a different resource for the HARQ-ACK assigned to be transmitted for the first PDSCH if the HARQ-ACK for the two PDSCHs are associated with HARQ-ACK codebooks of different priorities.

For any two HARQ process IDs in the scheduled cell, if the wireless device is scheduled to start receiving a first PDSCH starting in symbol j by a PDCCH ending in symbol i, the wireless device may not be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH that ends later than symbol i. According to an example, in the scheduled cell, for any PDSCH corresponding to system information RNTI (SI-RNTI), the wireless device may not decode a re-transmission of an earlier PDSCH with a starting symbol less than N symbols after the last symbol of that PDSCH, where the value of N may at least depend on the PDSCH subcarrier spacing configuration μ, with N=13 for μ=0, N=13 for μ=1, N=20 for μ=2, and N=24 for μ=3.

HARQ protocol may be a primary way of handling retransmissions in a wireless technology, e.g., New Radio (NR). In case of an erroneously received packet, a retransmission may be required. In HARQ protocol with soft combining, a wireless device may store an erroneously received packet (e.g., transport block) in a (soft) buffer memory, and later combine the received packet with one or more retransmissions to obtain a single, combined packet/transport block that may improve the successful decoding probability of the packet. In an example, decoding of the error-correction code operates on the combined signal. One or more retransmissions of a transport block may be handled by the physical layer and/or the MAC layer. In an example, large transport block (TB) sizes may be segmented into multiple codeblocks prior to coding, each with its own CRC, in addition to an overall TB CRC. Errors may be detected on individual codeblocks based on their CRC, as well as on the overall TB. The base station may configure the wireless device with retransmissions based on groups of codeblocks, e.g., codeblock groups (CBGs). If per-CBG retransmission is configured, feedback is provided pre CBG. A TB may comprise of one or more CBGs. A CBG that a codeblock belongs to may be determined based on an initial transmission and may be fixed.

A transmitting node (e.g., a base station) may perform rate matching for each code block. In an example, the base station may write coded bits into a circular buffer. The coded bits may start with non-punctured systematic bits and continue with parity bits. The base station may select transmit bits based on reading a required number of bits from the circular buffer. The exact selected bits for transmission may depend on an RV (e.g., RV0, RV1, RV2 or RV3) corresponding to a different starting position in the circular buffer.

In the downlink, one or more retransmissions may be scheduled in a same way as new downlink data (e.g., downlink assignment/transmission/signal/channel). For example, the one or more retransmissions may be scheduled at any time and any frequency location within a downlink cell and/or an active downlink BWP of a cell. In an example, a HARQ mechanism typically comprises multiple stop-and-wait protocols, each operating on a single transport block. In a stop-and-wait protocol, a transmitter stops and waits for an acknowledgment after each transmitted transport block. This protocol requires a single bit indicating positive or negative acknowledgment of the transport block; however, the throughput is low due to waiting after each transmission. Multiple stop-and-wait processes may operate in parallel, e.g., while waiting for acknowledgment from one HARQ process, the transmitter may transmit data of another HARQ process. The multiple parallel HARQ processes may form a HARQ entity, allowing continuous transmission of data. A wireless device may have one HARQ entity per carrier. A HARQ entity may support spatial multiplexing of more than four layers to a single device in the downlink, where two transport blocks may be transmitted in parallel on the same transport channel. The HARQ entity may have two sets of HARQ processes with independent HARQ acknowledgments.

In an example, upon receiving a downlink transmission scheduled via a DCI, the wireless device may attempt to decode a TB the downlink scheduling transmission is carrying, e.g., after soft combining with previous attempts/receptions of the TB. New downlink transmission and one or more downlink retransmissions may be scheduled in a same framework. The wireless device may determine whether a downlink transmission is a new transmission, or a retransmission based on an NDI field in a DCI indicating the downlink transmission. An explicit NDI may be included for the scheduled TB as part of the scheduling information in the downlink. The NDI field may comprise one or more NDI bits per TB (and/or CBG). The NDI bit may be toggled for a new transmission, and not toggled for a retransmission. In case of a new transmission, the wireless device flushes the soft buffer corresponding to the new transmission before receiving/storing the new transmission. In case of a retransmission, the wireless device may perform a soft combining of the received data (e.g., downlink retransmission) with stored data in the soft buffer for a corresponding HARQ process.

In an example, a time gap/interval/offset (e.g., K1) from a downlink data reception (e.g., DL-SCH resource) to a transmission of a HARQ ACK/NACK corresponding to the downlink data may be fixed, e.g., multiple subframes/slots/symbols. This scheme with pre-defined timing instants for the HARQ ACK/NACK may not blend well with dynamic TDD and/or unlicensed operation. A more flexible scheme, capable of dynamically controlling the HARQ ACK/NACK transmission timing may be adopted. For example, a DCI format may comprise a PDSCH-to-HARQ_feedback timing field to control/indicate a transmission timing of an HARQ ACK/NACK corresponding to a data scheduled by the DCI in an uplink transmission (e.g., PUCCH). The PDSCH-to-HARQ_feedback timing field in the DCI may be used as an index of one or more indexes of K1 values in a pre-defined and/or an RRC-configured table (e.g., a HARQ timing table). In an example, the K1 value may provide information of a gap/interval/offset between a second time to transmit the HARQ ACK/NACK relative to a first time of the downlink data reception. The wireless device may determine a resource for HARQ ACK/NACK transmission, e.g., frequency resource and/or PUCCH format and/or code domain, based on a location of a PDCCH (e.g., a starting control channel element (CCE) index) carrying the DCI format. The DCI format may comprise a field, e.g., PUCCH resource indicator (PRI) field, that indicates a frequency resource for an uplink transmission of the HARQ ACK/NACK transmission. For example, the PRI field may be an index selecting one of a plurality of pre-defined and/or RRC-configured PUCCH resource sets.

In an example, a wireless device may multiplex a plurality of HARQ feedback bits that are scheduled for transmission in the uplink at a same time/slot, for example, in a carrier aggregation scenario and/or when per-CBG retransmission is configured. The wireless device may multiplex multiple ACK/NACK bits of multiple TBs and/or CBGs into one multi-bit HARQ feedback message/codebook. In an example, the multiple ACK/NACK bits may be multiplexed based on a semi-static codebook and/or a dynamic codebook.

The semi-static codebook may be viewed as a matrix consisting of a time domain dimension and a component-carrier (and/or CBG and/or MIMO layer) dimension, both of which may be semi-statically configured and/or pre-defined. Each entry of the matrix may represent a decoding outcome, e.g., positive (ACK) or negative (NACK) acknowledgments, of the corresponding transmission. One or more of the entries of the codebook matrix may not correspond to a downlink transmission opportunity (e.g., a PDSCH occasion), for which a NACK is reported. This may increase a codebook robustness, e.g., in case of missed downlink assignments, and the base station may schedule a retransmission of missing TB(s)/CBG(s). In an example, the size of the semi-static codebook may be very large. The dynamic codebook may be used to address the large size of the semi-static codebook. With the dynamic codebook, only the ACK/NACK information of scheduled assignments, including one or more semi-persistent scheduling (SPS), may be included in the report. In an example, the size of the dynamic codebook may be dynamically varying, e.g., as a function of a number of scheduled carriers and/or as a function of a number of scheduled transport blocks.

In an example, HARQ-ACK information corresponding to different PDSCHs scheduled by a single DCI may be carried by different PUCCH(s), e.g., in different slots. In an example, the DCI may indicate HARQ-ACK timing earlier than the PDSCH processing time for the last PDSCH(s). For a wireless device and a serving cell, scheduling multiple PDSCHs by a first DCI and scheduling multiple PUSCHs by a second DCI may be supported. Each PDSCH/PUSCH may have individual/separate TB(s). Each PDSCH (or PUSCH) may be confined within a slot. A maximum number of M (e.g., M=8 or 16 or 32) PDSCHs (or PUSCHs) may be scheduled with the first DCI (or the second DCI). For multi-PUSCH (or multi-PDSCH) scheduling, a time domain resource allocation (TDRA) table may be configured such that each row indicates up to X multiple PUSCHs (or PDSCHs), which may be continuous and/or non-continuous in time domain. Each PUSCH (or PDSCH) may have a separate start and length indicator value (SLIV) and mapping type. In an example, a number of the scheduled PUSCHs (or PDSCHs) may be signaled by a number of indicated valid SLIVs in the row of the TDRA table signaled via the first DCI (or the second DCI).

Semi-persistent scheduling (SPS) may be supported in the downlink, where the wireless device may be configured with a periodicity of the data transmission using RRC signaling. Activation of semi-persistent scheduling may be done using PDCCH, as for dynamic scheduling, for example, with CS-RNTI. The PDCCH may carry necessary information in terms of time-frequency resources and other parameters. A HARQ process number/ID may be derived from a time, for example, when the downlink data transmission starts. Upon activation of semi-persistent scheduling, the wireless device may receive downlink transmission periodically according to an RRC-configured periodicity using the transmission parameters indicated in the PDCCH activating the transmission.

In the uplink, two schemes for transmission without a dynamic grant may be supported. The two schemes may differ in the way they are activated: 1) configured grant type 1 (or Type 1 configured grant), where an uplink grant is provided by RRC, including activation of the grant, 2) configured grant type 2 (or Type 2 configured grant), where the transmission periodicity is provided by RRC and L1/L2 control signaling is used to activate/deactivate the transmission in a similar way as in a downlink case. The two schemes may reduce control signaling overhead, and the latency before uplink data transmission, as no scheduling request-grant cycle is needed prior to data transmission. Configured grant type 2 may be similar to downlink SPS. RRC signaling may be used to configure the periodicity and PDCCH activation may provide transmission parameters. Upon receiving the activation command, the wireless device may transmit according to the preconfigured periodicity, if, for example, there are data in the buffer. If there are no data to transmit, the wireless device may, similarly to type 1, not transmit anything. The wireless device may acknowledge the activation/deactivation of type 2 by sending a MAC control element in the uplink. In both schemes, it is possible to configure multiple wireless devices with overlapping time-frequency resources in the uplink. In this case, the network may differentiate between transmissions from different wireless devices. In an example, PUSCH resource allocation may be semi-statically configured by higher layer parameter configuredGrantConfig in BWP-UplinkDedicated information element. The PUSCH transmission may be corresponding to a configured grant. In an example, the higher layer configured parameters repK and repK-R V may define the K repetitions to be applied to a transmitted transport block, and the redundancy version pattern to be applied to K repetitions. In an example, for Type 1 and Type 2 PUSCH transmissions with a configured grant, when the UE is configured with repK>1, the wireless device may repeat a TB across the repK consecutive slots applying the same symbol allocation in each slot.

In an example, the wireless device may not transmit on the resources configured by configuredGrantConfig if the higher layers did not deliver a transport block to transmit on the resources allocated for uplink transmission without grant.

In an example, a wireless device, when supporting high reliability and low latency services, may be configured for a bundling operation with repetition transmission (e.g., pusch-AggregationFactor or pdsch-AggregationFactor larger than 1), in which a same symbol allocation may be applied across the repetition transmission (e.g., the same symbol allocation may be applied across pusch-AggregationFactor or pdsch-AggregationFactor consecutive slots). The wireless device may expect that a transport block (TB) be repeated within each symbol allocation among each of the pusch-AggregationFactor or pdsch-AggregationFactor consecutive slots. In an example, the bundling operation may rely on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle. For example, after the initial transmission, pdsch-AggregationFactor−1 HARQ retransmissions follow within a bundle.

In an example, a wireless device may support a baseline processing time/capability. Some wireless devices may support additional aggressive/faster processing time/capability. In an example, the wireless device may report to a base station a processing capability, e.g., per sub-carrier spacing. In an example, a PDSCH processing time may be considered to determine, by a wireless device, a first uplink symbol of a PUCCH (e.g., determined at least based on a HARQ-ACK timing K1 and one or more PUCCH resources to be used and including the effect of the timing advance) comprising the HARQ-ACK information of the PDSCH scheduled by a DCI. In an example, the first uplink symbol of the PUCCH may not start earlier than a time gap (e.g., T_(proc,1)) after a last symbol of the PDSCH reception associated with the HARQ-ACK information. In an example, the first uplink symbol of the PUCCH which carries the HARQ-ACK information may start no earlier than at symbol L1, where L1 is defined as the next uplink symbol with its Cyclic Prefix (CP) starting after the time gap T_(proc1)=(N₁+d_(1,1)+d₂)(2048+144).α₁ after the end of the last symbol of the PDSCH. In an example, parameter al may depend on a numerology μ. The time gap may be given by the wireless device PDSCH processing capability in the corresponding frequency band. In an example, d_(1,1) may at least depend on the PDSCH mapping (e.g., a mapping type A or mapping type B) and the length of the PDSCH (in the number of symbols). In an example, the wireless device may set d₂=0.

FIG. 18 shows example PDSCH processing times. Table 1 shows PDSCH decoding time (N1) in number of symbols for a first PDSCH processing capability and for different numerologies. Table 2 shows PDSCH decoding time in number of symbols for a second PDSCH processing capability and for different numerologies. As shown in FIG. 18 , for PDSCH processing capability 1, PDSCH decoding time N1 is more than 14 OFDM symbols if SCS is higher than 60 kHz (μ=2). Even for PDSCH processing capability 2, PDSCH decoding time N1 is 9 OFDM symbols for 60 kHz SCS. The PDSCH decoding time, N1, for 480 kHz and 960 kHz SCS may be more than 14 OFDM symbols (1 slot). In an example, parameter N1 may be based on μ for the wireless device with processing capability 1 and 2 respectively, where μ may correspond to the one of (μ_(PDCCH), μ_(PDSCH), μ_(UL)). For example, the μ_(PDCCH) corresponds to the subcarrier spacing of the PDCCH scheduling the PDSCH, the μ_(PDSCH) corresponds to the subcarrier spacing of the scheduled PDSCH, and μ_(UL) corresponds to the subcarrier spacing of the uplink channel with which a HARQ-ACK is to be transmitted.

In an example, an PUSCH preparation/processing time may be considered for determining the transmission time of an UL data. For example, if the first uplink symbol in the PUSCH allocation for a transport block (including the DM-RS) may not be no earlier than at symbol L2, the wireless device may perform transmitting the PUSCH. In an example, the symbol L2 may be determined, by a wireless device, at least based on a slot offset (e.g., K2), SLIV of the PUSCH allocation indicated by time domain resource assignment of a scheduling DCI. In an example, the symbol L2 may be specified as the next uplink symbol with its CP starting after a time gap with length T_(proc,2)=max ((N₂+d_(2,1)+d₂)(2048+144).α₁, d_(2,2)) after the end of the reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH. If the first symbol of the PUSCH allocation consists of DM-RS only, the wireless device may set d_(2,1)=0, otherwise d_(2,1)=1. In an example, parameter a₁ may depend on a numerology μ.

FIG. 19 shows examples of PUSCH preparation/processing time. Table 3 in FIG. 19 shows example PUSCH preparation/processing time in number of slots (N2) for a wireless device with PUSCH timing capability 1. Table 4 in FIG. 19 shows example PUSCH preparation/processing time in number of slots (N2) for a wireless device with PUSCH timing capability 2. As FIG. 19 shows N2 may depend on the numerology μ. In an example, the numerology μ may correspond to the subcarrier spacing of the downlink with which a PDCCH carrying a DCI scheduling a PUSCH is transmitted. In another example, the numerology μ may correspond to the subcarrier spacing of the uplink channel with which the PUSCH is to be transmitted.

In an example, a wireless device may not decode a PDSCH in a serving cell scheduled by a PDCCH with C-RNTI, CS-RNTI or MCS-C-RNTI and one or multiple PDSCH(s) required to be received (e.g., via CA) in the same serving cell without a corresponding PDCCH transmission if the PDSCHs partially or fully overlap in time. The wireless device may decode the PDSCH if the PDCCH scheduling the PDSCH ends at least 14 symbols before the earliest starting symbol of the PDSCH(s) without the corresponding PDCCH transmission. The symbol duration may be determined based on the smallest numerology between the scheduling PDCCH and the PDSCH. According to an example, the wireless device may not decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI if another PDSCH in the same cell scheduled with RA-RNTI or MSGB-RNTI partially or fully overlap in time.

A wireless device may, upon detection of a PDCCH with a configured DCI format 0_0, 0_1 or 0_2, may transmit the corresponding PUSCH as indicated by that DCI unless the wireless device does not generate a transport block. In an example, when the wireless device is scheduled with multiple PUSCHs by a DCI, HARQ process ID indicated by the DCI may apply to the first PUSCH, HARQ process ID is then incremented by 1 for each subsequent PUSCH(s) in the scheduled order. For any HARQ process ID(s) in a scheduled cell, the wireless device may not transmit a PUSCH that overlaps in time with another PUSCH. For any two HARQ process IDs in the scheduled cell, if the wireless device is scheduled to start a first PUSCH transmission starting in symbol j by a PDCCH ending in symbol i, the wireless device may not transmit a PUSCH starting earlier than the end of the first PUSCH by a PDCCH that ends later than symbol i. In an example, the wireless device may not transmit another PUSCH by DCI format 0_0, 0_1 or 0_2 scrambled by C-RNTI or MCS-C-RNTI for a HARQ process until after the end of the expected transmission of the last PUSCH for the HARQ process.

In an example, a wireless device may not be scheduled by a PDCCH ending in symbol i to transmit a first PUSCH on the serving cell overlapping in time with a transmission occasion, where the wireless device is configured to transmit a second PUSCH with configured grant (e.g., Type 1 configured grant), starting in a symbol j if the end of symbol i is not at least N₂ symbols before the beginning of symbol j. In an example, a wireless device may not be scheduled by a first PDCCH ending in symbol i to transmit a first PUSCH on a given serving cell for a first HARQ process, if there is a transmission occasion where the wireless device is configured to transmit a second PUSCH with configured grant (e.g., Type 1 configured grant) with the first HARQ process on the same serving cell starting in a symbol j after symbol i, and if the gap between the end of the first PDCCH and the beginning of symbol j is less than N₂ symbols. In an example, the value N₂ in symbols may be determined in prat according to the wireless device's processing capability.

In an example, a plurality of slot format combinations of a cell (e.g., slot format combination 0, slot format combination 1, slot format combination 2, slot format combination 3, . . . , and slot format combination m) may be configured to a wireless device via RRC messages. In an example, a slot format combination may be indicated to a wireless device via downlink control channel. In an example, the slot format combination may be indicated to the wireless device via a PDCCH. In an example, the slot format combination may be indicated to the wireless device via a group common PDCCH (GC-PDCCH). In an example, a slot format may be_identified by a corresponding format index. In an example, each symbol in the slot may be a downlink (‘D’) symbol and/or an uplink (‘U’) symbol and/or a flexible (‘F’) symbol. For example, slot format 0 comprises of all downlink (‘D’) symbols. For example, slot format 1 comprises of all uplink (‘U’) symbols. For example, slot format 55 comprises of two downlink (‘D’) symbols, followed by three flexible (‘F’) symbols, followed by three uplink (‘U’) symbols, followed by six downlink (‘D’) symbols. In NR, each of symbols in a slot may be: Uplink (‘U’/UL), wherein uplink transmission is allowed; Downlink (‘D’/DL), wherein downlink reception is allowed; and Flexible (‘F’), wherein the slot format/direction is determined by other signaling, e.g., DCI format 2_0 and/or UL/DL grants. The format ‘F’ is used by the network to control UL/DL transmission of each wireless device flexibly. For example, the network may assign a symbol with ‘F’ for a wireless device not to transmit to or receive from a base station for interference control and/or power saving. For example, the network may use a slot format ‘F’ on one or more symbols to selectively initiate/trigger random access (RA) for a particular wireless device. Other wireless devices may not be allowed to transmit or receive on the one or more symbols, resulting in reduced interference for the wireless device.

A wireless device may be configured by higher layers with a parameter indicating one or more slot formats (e.g., SlotFormatlndicator). In an example, a DCI (e.g., DCI format 2_0) may be used for notifying the one or more slot formats. An SFI-index field value in the DCI format 2_0 may indicate to a wireless device a slot format for each of one or more slots in a number of slots for each DL BWP and/or each UL BWP starting from a slot where the wireless device detects the DCI. The DCI format may comprise CRC bits scrambled by a first radio network temporary_identifier (e.g., SFI-RNTI). The DCI format may comprise at least one information of one or more slot format indicators (SFIs). The wireless device may be configured to monitor a group-common-PDCCH for the one or more slot format indicators for each one of one or more serving cells configured by the parameters indicating the one or more slot formats. For each serving cell, the wireless device may be provided at least one of: an_identity of the serving cell; a location of an SFI-index field in the DCI; and/or a set of slot format combinations comprising one or more slot format combinations (e.g., slotFormatCombinations), where each of the one or more slot format combinations may comprise: one or more slot formats (e.g., slotFormats) for the slot format combination; a mapping for the slot format to a corresponding SFI-index field value in the DCI (e.g., slotFormatCombinationId); and/or at least one reference SCS configuration.

In an example, for each serving cell, a wireless device may receive a common RRC configuration message (e.g., TDD-UL-DL-ConfigCommon) comprising one or more parameters that indicate to the wireless device to set the slot format of each slot of a number of one or more consecutive slots. For example, the common RRC configuration message may comprise at least one of: a reference subcarrier spacing (SCS) μ_(ref); and/or at least one pattern. A first pattern of the at least one pattern may comprise at least one of: a slot configuration period of P msec; a number of slots d_(slots) with only downlink symbols; a number of downlink symbols d_(sym); a number of slots μ_(slots) with only uplink symbols; a number of uplink symbols μ_(sym). The slot configuration period of P msec may comprise S=P. 2^(μref) slots with SCS configuration μ_(ref). From the S slots, a first d_(slots) slots may comprise one or more downlink symbols and a last μ_(slots) slots may comprise one or more uplink symbols. A d_(sym) symbols after the first d_(slots) slots may comprise one or more downlink symbols. A μ_(sym) symbols before the last μ_(slots) slots may comprise one or more uplink symbols. A remaining (S−d_(slots)−μ_(slots)).N_(symb) ^(slot)−d_(sym)−μ_(sym) symbols may comprise one or more flexible symbols. A second pattern of the at least one or more patterns may be configured. The wireless device may set the slot format of each slot of a first number of slots as indicated by the first pattern and may set the slot format of each slot of a second number of slots as indicated by the second pattern.

In an example, a wireless device may receive a dedicated RRC configuration message (e.g., TDD-UL-DL-Configdedicated) comprising one or more parameters that may overwrite one or more flexible symbols of each slot of a number of slots configured by a common RRC configuration message (e.g., TDD-UL-DL-ConfigCommon). For example, the dedicated RRC configuration message may comprise at least one of: one or more slot configurations; and/or for each slot configuration of the one or more slot configurations: a slot index for a slot (e.g., slotIndex); one or more symbols of a slot (e.g., symbols) which indicates a first number of zero or more downlink first symbols in the slot, and a second number of zero or more uplink last symbols in the slot, and a remaining number of zero or more flexible symbols in the slot. The wireless device may determine a slot format for each slot with a corresponding slot index of the slot with index slotIndex based on a format indicated by the one or more symbols of the slot (symbols). In an example, for each slot configuration of one or more slot configurations indicated by the dedicated RRC configuration message, a reference SCS is the reference SCS indicated by the common RRC configuration message. A slot configuration period and a number of downlink/uplink/flexible symbols in each slot of the one or more slot configuration period may be determined from the common/dedicated RRC configuration messages and may be common to each one of one or more configured BWPs.

A slot format determination procedure may be defined for the wireless device. The wireless device may determine a slot format of one or more symbols based on a priority between a first slot format indicated by higher layer parameters (e.g., TDD-UL-DL-ConfigCommon and/or TDD-UL-DL-ConfigDedicated) and a second slot format indicated by a DCI (e.g., DCI format 2_0), if detected. Whether the UL/DL grant is configured by higher layer or dynamically indicated by DCI, may be used by the wireless device to determine the slot format.

In an example, the wireless device may not receive the one or more RRC configuration messages (e.g., a common RRC configuration message and/or a dedicated RRC configuration message) indicating a slot format configuration. The wireless device may receive a DCI (e.g., DCI format 1_0, DCI format 1_1, DCI format 0_1, DCI format 0_0, and/or DCI format 2_3), scheduling downlink/uplink transmissions. In an example, a DCI (e.g., DCI format 1_0, DCI format 1_1, and/or DCI format 0_1) or an RRC message (e.g., SIB1) may indicate to the wireless device a reception of one or more downlink channels/signals e.g., PDSCH, PDCCH, SSB, downlink positioning reference signal (DL PRS) and/or CSI-RS in one or more symbols of a slot.

The wireless device may receive the one or more downlink channels/signals in the one or more symbols of the slot. In an example, the wireless device may receive a DCI (e.g., DCI format 1_0, DCI format 1_1, DCI format 0_0, DCI format 2_3, and/or DCI format 0_1) indicating a transmission of one or more uplink channels/signals (e.g., PUSCH, PUCCH, PRACH, and/or SRS) in one or more symbols of a slot. The wireless device may transmit the one or more uplink channels/signals in the one or more symbols of the slot. In an example, the wireless device may receive an RAR message 1312/1322/1332 (e.g., in response to and/or after transmitting Msg1 1311/1321 or MsgA 1331) indicating an UL grant for transmission of one or more uplink channels/signals (e.g., PUSCH) in one or more symbols of a slot. The wireless device may transmit the one or more uplink channels/signals in the one or more symbols of the slot. In another example, the wireless device may receive a fallbackRAR message 1332 (e.g., in response to and/or after transmitting MsgA 1331) indicating an UL grant for transmission of one or more uplink channels/signals (e.g., PUSCH) in one or more symbols of a slot. The wireless device may transmit the one or more uplink channels/signals in the one or more symbols of the slot. In another example, the wireless device may receive a successRAR message 1332 (e.g., in response to and/or after transmitting MsgA 1331) indicating the transmission of one or more uplink channels/signals (e.g., PUCCH) in one or more symbols of a slot. The wireless device may transmit the one or more uplink channels/signals in the one or more symbols of the slot.

In an example, a wireless device may be configured by higher layers (e.g., the MAC layer) to receive a downlink channel/signal (e.g., PDCCH, a PDSCH, a DL PRS, and/or a CSI-RS) in one or more symbols of a slot. The wireless device may receive the PDCCH, PDSCH, DL PRS, and/or CSI-RS, for example, if the wireless device does not detect a DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, and/or DCI format 2_3) indicating to the wireless device to transmit an uplink channel/signal (e.g., PUSCH, a PUCCH, a PRACH, and/or a SRS) in at least one symbol of the one or more symbols of the slot. The wireless device may not receive the downlink channel/signal, for example, if the wireless device detects a DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, and/or DCI format 2_3) indicating to the wireless device to transmit the uplink channel/signal in the at least one symbol of the one or more symbols of the slot.

In an example, for one or more symbols of a slot, a wireless device may not expect to detect a first DCI (e.g., DCI format 2_0) with an SFI-index field value indicating the one or more symbols of the slot as uplink and to detect a second DCI (e.g., DCI format 1_0, a DCI format 1_1, or DCI format 0_1) indicating to the wireless device to receive PDSCH or CSI-RS in the one or more symbols of the slot. In another example, for one or more symbols of a slot, the wireless device may not expect to detect the first DCI with an SFI-index field value indicating the one or more symbols in the slot as downlink and to detect a third DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, DCI format 2_3), a RAR UL grant, a fallbackRAR UL grant, or a successRAR indicating to the wireless device to transmit an uplink channel/signal (e.g., PUSCH, PUCCH, PRACH, or SRS) in the one or more symbols of the slot.

In an example, for one or more symbols of a slot that are indicated to a wireless device as uplink by one or more RRC configuration messages (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), the wireless device may not receive a downlink channel/signal (e.g., PDCCH, PDSCH, or CSI-RS) in the one or more symbols of the slot when the downlink channel/signal overlaps, even partially, with the one or more symbols of the slot. According to an example, for a set of symbols of a slot that are indicated to a UE as uplink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, the wireless device may not receive DL PRS in the set of symbols of the slot, if the wireless device is not provided with a measurement gap. According to an example, the wireless device may receive the DL PRS in the set of symbols of the slot, if the wireless device is provided with a measurement gap.

In an example, For the one or more symbols of the slot that are indicated to the wireless device as downlink by the one or more RRC configuration messages (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), the wireless device may not transmit an uplink channel/signal (e.g., PUSCH, PUCCH, PRACH, and/or SRS) in the one or more symbols of the slot when the uplink channel/signal overlaps, even partially, with the one or more symbols of the slot. In an example, for the one or more symbols of the slot that are indicated to the wireless device as flexible by the one or more RRC configuration messages (common and/or dedicated), the wireless device may not receive both dedicated configuring transmission from the wireless device in the one or more symbols of the slot and dedicated configuring reception by the wireless device in the one or more symbols of the slot.

In an example, for operation on a single carrier in unpaired spectrum, for one or more symbols of a slot indicated to a wireless device by one or more RRC parameters (e.g., ssb-PositionsInBurst in SIB1 or ssb-PositionslnBurst in ServingCellConfigCommon) for reception of SS/PBCH blocks, the wireless device may not transmit an uplink channel/signal (e.g., PUSCH, PUCCH, and/or PRACH) in the slot if a transmission overlaps with at least one symbol from the one or more symbols. In another example, for one or more symbols of a slot indicated to the wireless device by the one or more RRC parameters for reception of SS/PBCH blocks the wireless device may not transmit SRS in the one or more symbols of the slot. In another example, for one or more symbols of a slot indicated to the wireless device by the one or more RRC parameters for reception of SS/PBCH blocks, the wireless device may not expect the one or more symbols of the slot to be indicated as uplink by RRC configuration messages (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) when provided to the wireless device.

In an example, for one or more symbols of a slot corresponding to a valid PRACH occasion and N_gap symbols before the valid PRACH occasion, the wireless device may not receive a downlink channel/signal (e.g., PDCCH, PDSCH, or CSI-RS) in the slot if a reception overlaps with any symbol from the one or more symbols. The UE does not expect the one or more symbols of the slot to be indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

In an example, if a wireless device is scheduled by a first DCI (e.g., DCI format 1_1) to receive PDSCH over a plurality of slots, and if one or more RRC configuration parameters (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) indicate that, for a slot in the plurality of slots, at least one symbol from one or more symbols where the wireless device is scheduled PDSCH reception in the slot is an uplink symbol, the wireless device may not receive the PDSCH in the slot. In another example, if the wireless device is scheduled by a second DCI (e.g., DCI format 0_1) to transmit PUSCH over plurality of slots, and if the one or more RRC configuration parameters indicate that, for a slot from the plurality of slots, at least one symbol from one or more symbols where the wireless device is scheduled PUSCH transmission in the slot is a downlink symbol, the wireless device may not transmit the PUSCH in the slot. According to an example, for one or more symbols of a slot indicated to a wireless device by pdcch-ConfigSIB1 in MIB for a CORESET for Type0-PDCCH CSS set, the wireless device may not expect the one or more symbols to be indicated as uplink by the one or more RRC configuration parameters.

For one or more symbols of a slot that are indicated as downlink/uplink by RRC configuration messages (e.g., TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated), the wireless device may not detect a DCI (e.g., DCI format 2_0) with an SFI-index field value indicating the one or more symbols of the slot as uplink/downlink, respectively, or as flexible. In an example, for one or more symbols of a slot indicated to a wireless device by RRC messages (e.g., ssb-PositionslnBurst in ssb-PositionslnBurst) for reception of SS/PBCH blocks, the wireless device may not detect the DCI (e.g., DCI format 2_0) with an SFI-index field value indicating the one or more symbols of the slot as uplink. In another example, for one or more symbols of a slot indicated to a wireless device by RRC messages (e.g., prach-Configurationlndex in RACH-ConfigCommon) for PRACH transmissions, the wireless device may not detect the DCI (e.g., DCI format 2_0) with an SFI-index field value indicating the one or more symbols of the slot as downlink. In an example, for one or more symbols of a slot indicated to a wireless device by RRC messages (e.g., pdcch-ConfigSIB1 in MIB) for a CORESET for Type0-PDCCH CSS set, the wireless device may not detect the DCI (e.g., DCI format 2_0) with an SFI-index field value indicating the one or more symbols of the slot as uplink.

For one or more symbols of a slot indicated to a wireless device as flexible by RRC configuration messages (e.g., TDD-UL-DL-ConfigurationCornrnon and TDD-UL-DL-ConfigDedicated), or when RRC configuration messages are not provided to the wireless device, the wireless device may detect a DCI (e.g., DCI format 2_0) providing a format for the slot. If at least one symbol of the one or more symbols is a symbol in a CORESET is configured to the wireless device for PDCCH monitoring, the wireless device may receive PDCCH in the CORESET only if an SFI-index field value in the DCI indicates that the at least one symbol is a downlink symbol.

In an example, for one or more symbols of a slot indicated to a wireless device as flexible by RRC configuration messages (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated), or when RRC configuration messages are not provided to the wireless device, the wireless device may detect a DCI (e.g., DCI format 2_0) providing a format for the slot. If the SFI-index field value in the DCI indicates the one or more symbols of the slot as flexible and the wireless device detects a second DCI format (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) indicating to the wireless device to receive downlink channel/signal (e.g., PDSCH or CSI-RS) in the one or more symbols of the slot, the wireless device may receive the downlink channel/signal in the one or more symbols of the slot.

According to an example, for one or more symbols of a slot indicated to a wireless device as flexible by RRC configuration messages (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated), or when RRC configuration messages are not provided to the wireless device, the wireless device may detect a DCI (e.g., DCI format 2_0) providing a format for the slot. If the SFI-index field value in the DCI indicates the one or more symbols of the slot as flexible, and the wireless device does not detect a DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) indicating to the wireless device to receive a downlink channel/signal (e.g., PDSCH or CSI-RS), the wireless device may not transmit the downlink channel/signal in the one or more symbols of the slot. In an example, if the SFI-index field value in the DCI format indicates the one or more symbols of the slot as flexible and the wireless device detects a DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, DCI format 2_3), or a RAR UL grant, or a fallbackRAR UL grant, or a successRAR indicating to the wireless device to transmit an uplink channel/signal (e.g., PUSCH, PUCCH, PRACH, or SRS) in the one or more symbols of the slot, the wireless device may transmit the uplink channel/signal in the one or more symbols of the slot. In an example, the wireless device may not detect an SFI-index field value in a first DCI indicating the one or more symbols of the slot as downlink and also detect a second DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, DCI format 2_3), or a RAR UL grant, or a fallbackRAR UL grant, or a successRAR indicating to the wireless device to transmit an uplink channel/signal (e.g., SRS, PUSCH, PUCCH, or PRACH) in at least one symbol of the one or more symbols of the slot.

In an example, for one or more symbols of a slot indicated to a wireless device as flexible by RRC configuration messages (e.g., TDD-UL-DL-ConfigurationCornrnon and TDD-UL-DL-ConfigDedicated), or when RRC configuration messages are not provided to the wireless device, the wireless device may detect a DCI (e.g., DCI format 2_0) providing a format for the slot. If the wireless device is configured by higher layers to receive a downlink channel/signal (e.g., PDSCH or CSI-RS) in the one or more symbols of the slot, the wireless device may receive the downlink channel/signal in the one or more symbols of the slot only if an SFI-index field value in the DCI indicates the one or more symbols of the slot as downlink. In an example, if the wireless device is configured by higher layers to receive DL PRS in the one or more symbols of the slot, the wireless device may receive the DL PRS in the one or more symbols of the slot only if an SFI-index field value in the DCI format 2_0 indicates the set of symbols of the slot as downlink or flexible. According to an example, if the wireless device is configured by higher layers to transmit an uplink channel/signal (e.g., PUCCH, or PUSCH, or PRACH) in the one or more symbols of the slot, the wireless device transmits the uplink channel/signal in the slot only if an SFI-index field value in the DCI format indicates the one or more symbols of the slot as uplink. In an example, if the wireless device is configured by higher layers to transmit an SRS in the one or more symbols of the slot, the wireless device transmits the SRS only in a subset of symbols from the one or more symbols of the slot indicated as uplink symbols by an SFI-index field value in the DCI format.

In an example, for one or more symbols of a slot indicated to a wireless device as flexible by RRC configuration messages (e.g., TDD-UL-DL-ConfigurationCornrnon and TDD-UL-DL-ConfigDedicated), or when RRC configuration messages are not provided to the wireless device, the wireless device may detect a DCI (e.g., DCI format 2_0) providing a format for the slot. The wireless device may not expect to detect an SFI-index field value in the DCI indicating the one or more symbols of the slot as downlink or flexible if the one or more symbols of the slot includes at least one symbol corresponding to any repetition of a PUSCH transmission activated by an UL Type 2 grant PDCCH. In another example, a wireless device may not expect to detect an SFI-index field value in the DCI indicating the one or more symbols of the slot as uplink and detect a second DCI (e.g., DCI format 1_0 or DCI format 1_1 or DCI format 0_1) indicating to the wireless device to receive a downlink channel/signal (e.g., PDSCH or CSI-RS) in at least one symbol of the one or more symbols of the slot.

In an example, if a wireless device is configured by higher layers to receive a downlink channel/signal (e.g., CSI-RS or PDSCH) in one or more symbols of a slot and the wireless device detects a DCI (e.g., DCI format 2_0) with a slot format value that indicates a slot format with a subset of symbols from the one or more symbols as uplink or flexible, the wireless device may cancel the downlink channel/signal reception in the one or more symbols of the slot. According to an example, if the wireless device is configured by higher layers to receive the downlink channel/signal in one or more symbols of a slot and the wireless device detects a second DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, or DCI format 2_3) indicating to the wireless device to transmit an uplink channel/signal (e.g., PUSCH, PUCCH, SRS, or PRACH) in at least one symbol in the one or more symbols, the wireless device may cancel the downlink channel/signal reception in the one or more symbols of the slot. In another example, if the wireless device is configured by higher layers to receive a DL PRS in a set of symbols of a slot and the wireless device detects a DCI format 2_0 with a slot format value (e.g., other than 255) that indicates a slot format with a subset of symbols from the set of symbols as uplink, or the wireless device detects the second DCI indicating to the wireless device to transmit the uplink channel/signal in at least one symbol in the set of the symbols, the wireless device may cancel the DL PRS reception in the set of symbols of the slot.

In an example, for one or more symbols of a slot that are indicated as flexible by RRC configuration messages (e.g., TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated), or when the RRC configuration messages TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated are not provided to a wireless device, the wireless device may not detect a DCI (e.g., DCI format 2_0) providing a slot format for the slot. The wireless device may receive a downlink channel/signal (e.g., PDSCH or CSI-RS) in the one or more symbols of the slot if the wireless device receives a corresponding indication by a DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1). In another example, if the wireless device is configured by higher layers to receive the downlink channel/signal in the one or more symbols of the slot, the wireless device may not receive the downlink channel/signal in the one or more symbols of the slot. For example, if the wireless device is configured by higher layers to receive DL PRS in the one or more symbols of the slot, the wireless device may receive the DL PRS. In another example, the wireless device may transmit an uplink channel/signal (e.g., PUSCH, PUCCH, PRACH, or SRS) in the one or more symbols of the slot if the wireless device receives a corresponding indication by a DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, or DCI format 2_3).

FIG. 20A shows an example of a wireless device without partialCancellation capability transmitting an uplink channel/signal. The wireless device may be configured by higher layers (e.g., the MAC layer) to transmit the uplink channel/signal (e.g., a PUCCH, a PUSCH, or a PRACH) in one or more symbols of a slot (from time T1 to time T5 in FIG. 20A). The wireless device may receive a PDCCH carrying a DCI where a last symbol of a CORESET where the wireless device detects the DCI is occurred at time T0. In an example, the DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) may indicate to the wireless device to receive a downlink channel/signal (e.g., CSI-RS or PDSCH) at time T3. In an example shown in FIG. 20A, in at least one symbol of the one or more symbols of the slot the downlink channel/signal may (partially) overlap/collide with the uplink channel/signal (from time T3 to at time T4). The wireless device may not cancel transmitting the UL channel/signal (including an actual repetition of the PUSCH) based on determining that the first symbol of the UL channel/signal (e.g., at time T1) is within a time window. In an example, the time window may start from a last symbol of the CORESET that the wireless device detected the DCI (at time T0 in FIG. 20A). The length of the time window may, for example, be determined, by the wireless device, at least based on the PUSCH preparation/processing time for the corresponding wireless device processing capability. As shown in FIG. 20A the length of the time window is T_(proc,2) In an example, T_(proc,2) may be evaluated assuming d_(2,1)=1 and a numerology μ that may correspond to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configuration of PUCCH and PUSCH or μ_(r), where μ_(r) corresponds to the SCS configuration of the PRACH if it is 15 kHz or higher; otherwise μ_(r)=0. As shown in FIG. 20A, the wireless device may not perform receiving the downlink channel/signal based on the determining that the first symbol of the UL channel/signal is occurred within the window.

FIG. 20B shows an example of a wireless device without partialCancellation capability transmitting an UL channel/signal. The wireless device may be configured by higher layers (e.g., the MAC layer) to transmit the uplink channel/signal (e.g., a PUCCH, a PUSCH, or a PRACH) in one or more symbols of a slot (from time T2 to time T5 in FIG. 20B). In an example shown in FIG. 20B, the wireless device may receive a PDCCH carrying a DCI with a last symbol at time T0. The DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) may indicate to the wireless device to receive a downlink channel (e.g., CSI-RS or PDSCH) at time T3. As FIG. 20B shown, the downlink channel/signal may collide with the uplink channel/signal in at least one symbol of the one or more symbols of the slot (from time T3 to time T4). The wireless device may cancel transmitting the UL channel/signal based on determining that the first symbol of the UL channel/signal (e.g., at time T2) is occurred outside the time window. The time window started from a last symbol of a CORESET where the wireless device detects the DCI (at time T0) with length T_(proc,2). As shown in FIG. 20B, the wireless device may receive the downlink channel/signal at time T3 based on the determining that the first symbol of the UL channel/signal is not within the window.

FIG. 21A shows an example of a wireless device with partialCancellation capability transmitting an UL channel/signal. The wireless device may be configured by higher layers (e.g., the MAC layer) to transmit the uplink signal (e.g., a PUCCH, a PUSCH, or a PRACH) in one or more symbols of a slot (from time T1 to time T5 in FIG. 21A). The wireless device may receive a PDCCH carrying a DCI with the last symbol at time T0. The DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) may indicate to the wireless device to receive a downlink channel/signal (e.g., CSI-RS or PDSCH) at time T3 in at least one symbol of the one or more symbols of the slot (from time T3 to time T4 in FIG. 21A), colliding (partially) with the UL channel/signal. As shown in FIG. 21A, the wireless device may partially transmit the UL channel/signal by transmitting the one or more symbols that are within the time window (started from time T1 and ended at time T2) based on determining that the first symbol of the UL channel/signal (e.g., at time T1) is within the time window with length T_(proc,2). In an example, the wireless device may cancel transmitting the one or more symbols of the UL channel/signal that are outside the time window. As shown in FIG. 21A, the wireless device, based on determining that the first symbol of the UL channel/signal is within the time window, may receive the downlink signal/channel at time T3. In an example, if the wireless device does not indicate partialCancellation capability, the wireless device may cancel transmitting the UL channel/signal in the one or more symbols based on determining that the first symbol of the UL channel/signal is not occurred within the time window. Based on determining that the transmission of the UL signal/channel being cancelled in the one or more symbols of the slot, the wireless device may receive the downlink channel/signal.

FIG. 21B shows an example of a wireless device transmitting an SRS. The wireless device may be configured by higher layers (e.g., the MAC layer) to transmit an SRS in one or more symbols of a slot (from time T1 to time T5 in FIG. 21B). In an example shown in FIG. 21B, the wireless device may receive a PDCCH carrying a DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) indicating to the wireless device to receive a downlink channel/signal (e.g., CSI-RS or PDSCH). The downlink channel/signal may collide (partially) with the SRS transmission in at least one symbol of the one or more symbols of the slot (from time T3 to time T4 in FIG. 21B). As shown in FIG. 21B, the wireless device may partially transmit the SRS transmission by transmitting the one or more symbols that are within the time window (started from time T1 and ended at time T2) based on determining that the first symbol of the UL channel/signal (e.g., at time T1 in FIG. 21B) is within the time window with length T_(proc,2) from a last symbol of the DCI. In an example, the wireless device may cancel the SRS transmission of one or more symbols that are occurred outside the time window. As shown in FIG. 21B, the wireless device, based on determining that the first symbol of the SRS transmission is within the time window, may receive the downlink channel/signal at time T3. In another example, if the wireless device does not indicate partialCancellation capability, the wireless device may cancel the SRS transmission in the one or more symbols based on determining that the first symbol of the SRR is occurred outside the time window (relative to a last symbol of a CORESET where the UE detects the DCI). In an example, based on cancelling the SRS transmission in the one or more symbols, the wireless device may receive the downlink channel/signal.

A non-terrestrial network (NTN) network (e.g., a satellite network) may be a network or network segment that uses a space-borne vehicle to embark a transmission equipment relay node (e.g., radio remote unit) or a base station (e.g., an NTN base station). While a terrestrial network is a network located on the surface of the earth, an NTN may be a network which uses an NTN node (e.g., satellite) as an access network, a backhaul interface network, or both. In an example, an NTN may comprise one or more NTN nodes/space-borne vehicles. An NTN node may embark a bent pipe payload (e.g., transparent payload) or a regenerative payload. The NTN node with transparent payload may comprise transmitter/receiver circuitries without the capability of on-board digital signal processing (e.g., modulation and coding). The NTN node may comprise a regenerative payload transmitter/receiver with the on-board processing used to demodulate and decode the received signal and/or regenerate the signal before sending it back to the earth.

In an example, the NTN node may be a satellite, a balloon, an air ship, a high-altitude platform station (HAPS), an unmanned aircraft system (UAS), and the like. FIG. 22 is an example figure of different types of NTN platforms/nodes. In an example, a satellite may be placed into a low-earth orbit (LEO) at an altitude between 250 km to 1500 km, with orbital periods ranging from 90-130 minutes. From the perspective of a given point on the surface of the earth, the position of the LEO satellite may change. In an example, a satellite may be placed into a medium-earth orbit (MEO) at an altitude between 5000 to 20000 km, with orbital periods ranging from 2 hours to 14 hours. In an example, a satellite may be placed into a geostationary satellite earth orbit (GEO) at 35,786 km altitude, and directly above the equator. From the perspective of a given point on the surface of the earth, the position of the GEO may not move.

FIG. 23 shown an example of an NTN with a transparent NTN platform/node. In an example, the NTN node (e.g., a satellite) may forward a received signal from another satellite (e.g., over inter-link satellite communication links) or a gateway on the ground (e.g., over the feeder communication link) back to the earth. The NTN node may forward a received signal from a wireless device on the earth to another NTN node or a gateway on the ground. The signal may be forwarded back with amplification and/or a shift between service link frequency (point or a bandwidth) and feeder link frequency.

An NTN may generate one or more beams over a given area (e.g., a coverage area or a cell). The footprint of a beam (or a cell) may be referred to as a spotbeam. For example, the footprint of a cell/beam may move over the Earth's surface with the satellite movement. The footprint of a cell/beam may be Earth fixed with some beam pointing mechanism used by the satellite to compensate for its motion. As shown in FIG. 22 , the size of a spotbeam may depend on the system design and may range from tens of kilometers to a few thousand kilometers.

In an example, a propagation delay (e.g., between a satellite and the ground or between multiple satellites) may be the amount of time it takes for the head of the signal to travel from a sender to a receiver or vice versa. For uplink, the sender may be a wireless device and the receiver may be a base station/access network. For downlink, the sender may be a base station/access network and the receiver may be a wireless device. The propagation delay may vary depending on a distance between the sender and the receiver, e.g., due to movement of the NTN node, movement of the wireless device, and/or feeder link switching.

FIG. 24 shows examples of propagation delay corresponding to NTNs of different altitudes. The propagation delay in the figure may be one-way latency. In an example, one-way latency may be an amount of time required to propagate through a telecommunication system from a terminal to the receiver (e.g., base station). In an example shown in FIG. 23 , for the transparent NTN, the round-trip propagation delay (RTD) may comprise service link delay (e.g., between the NTN node and the wireless device), feeder link delay (e.g., between the NTN gateway and the NTN node), and/or between the gateway and the base station in the case the gateway and the base station are not collocated. From FIG. 24 , in case of GEO satellite with transparent payload the RTD may be four times of 138.9 milliseconds (approximately 556 milliseconds). In an example, a RTD of a terrestrial network (e.g., NR, E-UTRA, LTE) may be negligible compared to the RTD of an NTN scenario. The RTD of a terrestrial network may be less than 1 millisecond. In an example, the RTD of a GEO satellite may be hundreds of times longer than the one of terrestrial network. A maximum RTD of a LEO satellite with transparent payload with altitude of 600 km may be 25.77 milliseconds. The differential RTD may be 3.12 milliseconds. In an example, for a LEO satellite with transparent payload with altitude of 1200 km, the maximum RTD of may be 41.77 milliseconds. The differential RTD may be 3.18 milliseconds.

As shown in FIG. 23 , the differential RTD within a beam/cell of the satellite may be calculated based on the maximum diameter of the beam/cell footprint at nadir (e.g., the maximum delay link). In an example, the differential RTD may imply the difference between communication latency that two wireless devices, e.g., a second wireless device (UE2) that is located close to the edge of the cell/beam and a first wireless device (UE1) that is located close to the center of the cell/beam, may experience while communicating with an NTN node. The first wireless device may experience a smaller RTD compared to the second wireless device. The link with maximum propagation delay may experience higher propagation delay than UE1 and UE2 in the cell/beam. The link to a cell/beam center may experience the minimum propagation delay in the cell/beam.

FIG. 23 also shows several examples of a reference point in an NTN architecture. In an example, the base station may configure the reference point at the cell/beam center (Case1). In an example of Case1, the reference point may be on the ground and have an altitude larger than all the wireless devices in the cell/beam in order to make sure that the propagation delay to the reference point stays the smallest propagation delay in the cell/beam. In another example, the base station may configure the reference point at the NTN node (Case2). In another example, the base station may configure the reference point within the feeder link between the NTN node and the gateway (Case3). In another example, the base station may configure the reference point at the gateway (Case4). In another example, the base station may configure the reference point at the base station (Case5). The reference point of an NTN may be provided to one or more wireless devices in order to facilitate the estimation of the propagation delay (e.g., in the service link) via one or more measurements by a wireless device.

In an example, the propagation delay between the base station and the reference point in FIG. 23 may be considered as common delay of the cell/beam (e.g., the delay that is experienced by all the wireless devices in the cell/beam). The base station may provide the value of the common delay to all wireless devices in the cell/beam via broadcast signaling (e.g., SIB1) allowing the wireless devices (e.g., with GNSS capability) to estimate their corresponding RTD through conducting/performing the one or more measurements. In another example, for one or more wireless devices that do not support GNSS capability (or their location estimation may not be accurate), the base station may configure the common delay equal to the maximum link of the cell/beam (see FIG. 23 ). In another example, the one or more measurements may allow the wireless devices to estimate/calculate the RTD or a portion of RTD via timestamp of a configured broadcast signal.

In an example, the NTN may provide resources/signaling in order to compensate for the changes that may happen to the value of the common delay as a result of the movement of the NTN node (e.g., LEO satellite), feeder link switch, or the change in the location of the reference point (e.g., Case 3 in FIG. 23 ).

Transmissions from different wireless devices in a cell/beam may need to be time-aligned at the base station and/or the NTN node (e.g., satellite) to maintain uplink orthogonality. Time alignment may be achieved by using different timing advance (TA) values at different wireless devices to compensate for their different propagation delays/RTDs. In an example, a wireless device may be configured to pre-compensate only part of the RTD, e.g., depending on the location of the reference point (Case1 to Case5 in FIG. 23 ). For example, when the reference point is located over the feeder link (Case3 in FIG. 23 ) the base station may partially pre-compensate the delay (between the base station and the reference point) and leave the compensation of the delay from the reference point to the wireless device to the wireless device.

For example, the wireless device may be provided by the orbital movement of the satellites (e.g., ephemeris of the satellites) or other required information. The ephemeris of the satellite may provide the wireless device with the movement pattern of the satellite allowing the wireless device to estimate the service link delay or the TA value over a time period. In an example, the ephemeris may be periodically broadcasted by the satellite along with an indication indicating the rate by which the TA calculations carried out by the wireless device using the ephemeris should be updated in order to account for the movement of the satellite.

As a result of a long propagation delay in an NTN scenario, solutions to avoid reduction in peak data rates, e.g., due to the stop-and-wait feature of HARQ procedure, in NTN may be required. In an example, to avoid stop-and-wait in HARQ procedure, the number of HARQ processes may be increased compared to TN systems (e.g., increased from 16 to 32) to match the longer NTN round trip delay. In another example, the base station may disable (e.g., via semi-statis configuration, MAC CE, or DCI) uplink HARQ feedback for one or more HARQ processes to avoid the stop-and-wait in HARQ procedure.

FIG. 25 shows an example of downlink communication between a base station and a wireless device in an NTN scenario with a feedback disabled HARQ process. The wireless device may be configured by means of RRC configuration, MAC CE, or DCI indicating one or more feedback disabled HARQ processes. As shown in FIG. 25 , the wireless device receives one or more configuration parameters indicating that a HARQ process with ID i is feedback disabled. Disabling feedback mechanism of the HARQ process i may allow the base station to schedule one or more downlink channels/signals (PDSCH or CSI-RS) associated with the HARQ process i without waiting for receiving corresponding HARQ-ACK/NACK information bits from the wireless device. The retransmission of downlink data without waiting for the HARQ information may be regarded as blind retransmission.

As FIG. 25 shows, the wireless device may receive a first DCI (e.g., DCI format 1_0,

DCI format 1_1, or DCI format 0_1) at time T0 and a second DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) at time T1 both associated with the HARQ process with ID i. The first DCI may indicate scheduling of a first downlink channel/signal (PDSCH or CSI-RS) and the second DCI may indicate scheduling of a second downlink channel/signal (PDSCH or CSI-RS). The wireless device may receive the first downlink channel/signal at time T2 and the second downlink channel/signal at time T3. The base station may schedule the reception time of the second downlink channel/signal with respect to the reception time of the first downlink channel/signal with accordance to the processing capability of the wireless device (e.g., PDSCH processing capability). As shown in FIG. 25 , a time gap with a length at least T_(proc),i started from the last symbol of the first downlink channel/signal to the first symbol of the second downlink channel/signal may be configured, for example, to allow the wireless device to decode the first downlink channel/signal. In an example, the NDI field of the first DCI may be toggled and the NDI field of the second DCI may not be toggled. In this case, the second DCI may schedule a (blind) retransmission of a downlink data/packet conveyed via the first downlink channel/signal (new transmission). The wireless device may not transmit a first HARQ-ACK/NACK associated with the first downlink channel/signal reception regardless of whether it successfully decoded the downlink data or not. In another example, the NDI field of the first DCI may be toggled, and the NDI field of the second DCI may be toggled. In this case, both the first and the second DCIs schedule new transmissions.

FIG. 26 shows an example of downlink data transmission with a feedback disabled HARQ process between a base station and a wireless device in an NTN scenario. The wireless device may receive one or more configuration parameters (e.g., RRC, MAC CE, and/or DCI) indicating that a HARQ process with ID i is feedback disabled. As FIG. 26 shows the base station schedules a new transmission and three retransmissions of a downlink data/packet (e.g., one or more transport blocks) via a blind retransmission procedure. The wireless device may receive a first DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) indicating the new transmission (e.g., NDI bit being toggled) at time T0 associated with the HARQ process i, a second DCI indicating a first retransmission (e.g., NDI bit not being toggled) at time T3 associated with the HARQ process i, a third DCI indicating a second retransmission (e.g., NDI bit not being toggled) at time T6 associated with the HARQ process i, and a fourth DCI indicating a third retransmission (e.g., NDI bit not being toggled) at time T8 associated with the HARQ process i. The wireless device may receive a first downlink channel/signal (e.g., PDSCH or CSI-RS) at time T1, a second downlink channel/signal at time T4, a third downlink channel/signal at time T7, and a fourth downlink channel/signal at time T9.

As shown in FIG. 26 , the wireless device may expect the time gap between the first symbol of the second downlink channel/signal (e.g., the first retransmission) and the last symbol of the first downlink channel/signal (e.g., new transmission) be larger than a time gap (e.g., T_(proc,1)) that may be a function of the processing capability of the wireless device. In an example, the wireless device may expect the time gap between the first symbol of the second retransmission and the last symbol of the first retransmission be larger than the time gap. In an example, the wireless device may expect the time gap between the first symbol of the third retransmission and the last symbol of the second retransmission be larger than the time gap.

In an example, the wireless device may not be able to successfully receive the first downlink channel/signal (e.g., not successfully decoding the downlink data) at time T2 in FIG. 26 . The wireless device may not be required to transmit a HARQ-NACK to the base station based on the HARQ process i being feedback disabled. The wireless device may store the downlink data in a soft buffer associated with the HARQ process i. In an example, the wireless device may use the downlink data/packet received from the second downlink channel/signal with the downlink data in the soft buffer to decode the downlink data. In the example of FIG. 26 , the wireless may be able to decode the downlink data successfully at time T5. In an example, the base station may not know whether the wireless device successfully decoded the downlink data or not after the first retransmission. In another example, the base station may assume all four downlink channel/signal transmissions may be used for the wireless device to successfully decode the wireless device.

A wireless device may receive a DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) from a base station, indicating a downlink channel/signal (e.g., PDSCH or CSI-RS) carrying a downlink packet/data in a slot. The higher layers (e.g., the MAC layer) of the wireless device may indicate a transmission of an uplink channel/signal (e.g., PUSCH, PRACH, PUCCH, or SRS) in the slot, colliding/overlapping with the downlink signal/channel in at least one symbol in the slot. In an NTN scenario, the downlink signal/channel may be a (blind) retransmission of the downlink packet (e.g., the DCI may indicate a feedback disabled HARQ process that is used for at least one pervious downlink (re)transmissions). Based on existing technologies, the wireless device may cancel the uplink transmission or partially transmit the uplink channel/signal depending on, e.g., a capability of the wireless device, and/or the relative time of the first symbol of the uplink signal/channel transmission with respect to a last symbol of a CORESET that the wireless device detects the DCI. By not performing the uplink signal/channel transmission or by performing the partial transmission of the uplink signal/channel due to colliding/overlapping with the downlink channel/signal, the wireless device may unnecessarily increase the uplink data transmission latency. In an NTN scenario with (blind) retransmission in downlink, there is a need to improve the uplink data transmission when the uplink transmission collides/overlaps with a downlink signal/channel.

A wireless device may receive one or more configuration parameters. The one or more configuration parameters may indicate that a HARQ process i is feedback disabled. The wireless device may receive a DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1), from the base station, indicating a downlink channel/signal (e.g., PDSCH or CSI-RS) associated with the HARQ process i carrying a downlink packet/data (comprising one or more transport blocks (TBs)) in a slot. In an example, the downlink signal/channel may be a (blind) retransmission of the downlink packet. The wireless device may receive at least one previous (re)transmission of the downlink packet. The base station may schedule the downlink channel/signal without requiring receiving one or more HARQ-ACK/NACK information bits associated with the at least one previous (re)transmission. In an example, the higher layers (e.g., the MAC layer or RRC layer) of the wireless device may indicate a transmission of an uplink channel/signal (e.g., PUSCH, PRACH, PUCCH, or SRS) in the slot, colliding/overlapping with the downlink signal/channel in at least one symbol of the slot.

Based on certain aspects of this disclosure, the wireless device may be configured to cancel/drop the downlink channel/signal by transmitting the uplink channel/signal. Example embodiments, improve the uplink data transmission latency. In an example, for determining whether the wireless device may cancel transmitting the uplink channel/signal or partially transmit the uplink channel/signal, some aspects of this disclosure allows the wireless device to determine (1) whether the DCI indicates a new transmission (e.g., NDI bit being toggled) or a retransmission (e.g., NDI bit not being toggled); and (2) the decoding status of the downlink packet that is scheduled by the DCI in the case of the retransmission. In an example embodiment, based on determining that the downlink signal/channel is a retransmission of the downlink data/packet, and the downlink data/packet is successfully decoded, the wireless device may drop/cancel the downlink signal/channel in the at least one symbol of the slot. In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the uplink channel/signal in the slot. By transmitting the uplink channel/signal, the wireless device may improve the uplink data transmission latency.

In an example embodiment, the wireless device, based on determining that the downlink signal/channel is a retransmission of the downlink data/packet, and the downlink data/packet is successfully decoded, may ignore/drop the DCI. In an example, based on ignoring/dropping the DCI, the wireless device may perform the uplink transmission in the slot. By performing the uplink transmission in the slot, the wireless device may improve the uplink data transmission latency.

FIG. 27 shows an example embodiment of a wireless device communicating with an NTN base station, in accordance with certain aspects of the present disclosure. The wireless device may receive one or more configuration parameters. The one or more configuration parameters may indicate that a HARQ process i is feedback disabled. The wireless device may receive a DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1), from the base station, indicating a downlink channel/signal (e.g., PDSCH or CSI-RS) associated with the HARQ process i carrying a downlink packet/data (comprising one or more transport blocks (TBs)) in a slot. In an example, the downlink signal/channel may be a (blind) retransmission of the downlink packet. The wireless device may receive at least one previous (re)transmission of the downlink packet. The base station may schedule the downlink channel/signal without requiring receiving one or more HARQ-ACK/NACK information bits associated with the at least one previous (re)transmission. In an example, the higher layers (e.g., the MAC layer) of the wireless device may indicate a transmission of an uplink channel/signal (e.g., PUSCH, PRACH, PUCCH, or SRS) in the slot, colliding/overlapping with the downlink signal/channel in at least one symbol of the slot. In an example, the higher layers may indicate an actual repetition of the uplink channel/signal (e.g., PUSCH or PUCCH) in the slot.

In an example embodiment shown in FIG. 27 , the wireless device may determine the downlink signal/channel being a retransmission of the downlink data/packet and the downlink data/packet being successfully decoded. In response to determining that downlink signal/channel being a retransmission of the downlink data/packet and the downlink data/packet being successfully decoded, the wireless device may drop/cancel the downlink signal/channel in the at least one symbol of the slot. In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the uplink channel/signal in the slot. By transmitting the uplink channel/signal, the wireless device may improve the uplink data transmission latency.

In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the actual repletion of the uplink channel/signal, based on determining that the actual repletion of the uplink channel/signal being scheduled by the higher layers, in the slot. By transmitting the actual repetition of the uplink channel/signal, the wireless device may improve the uplink data transmission latency.

FIG. 28 shows an example embodiment of a wireless device with partialCancellation capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure. The wireless device may receive the one or more configuration parameters. As shown in FIG. 28 , the wireless device may receive the DCI. In an example, the higher layers (e.g., the MAC layer) of the wireless device may indicate a transmission of an uplink channel/signal (e.g., PUSCH, PRACH, PUCCH) in the slot, colliding/overlapping with the downlink signal/channel in at least one symbol of the slot. In an example, the higher layers may indicate a repetition of the uplink channel/signal (e.g., PUSCH or PUCCH) in the slot. In an example, the wireless device may determine that the first symbol of the uplink channel/signal is within a time window, started from a last symbol of a CORESET that the wireless device detects the DCI, with the length of T_(proc,2). In an example, T_(proc,2) may be specified assuming d_(2,1)=1 and a numerology μ that may correspond to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI and the SCS configuration of PUCCH and PUSCH or μ_(r), where y_(r) corresponds to the SCS configuration of the PRACH if it is 15 kHz or higher; otherwise μ_(r)=0.

In an example, based on determining that the downlink signal/channel is a retransmission of the downlink data/packet, the first symbol of the uplink channel/signal is within the time window, and the downlink data/packet is successfully decoded, the wireless device may drop/cancel the downlink signal/channel in the at least one symbol of the slot. In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the uplink channel/signal in the slot. By transmitting the uplink channel/signal, the wireless device may improve the uplink data transmission latency.

In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the actual repetition of the uplink channel/signal, based on the repletion of the uplink channel/signal being scheduled by the higher layers, in the slot. By transmitting the actual repetition of the uplink channel/signal, the wireless device may improve the uplink data transmission latency.

FIG. 29 shows an example embodiment of a wireless device with partialCancellation capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure. The wireless device may receive the one or more configuration parameters. As shown in FIG. 29 , the wireless device may receive the DCI from the base station. In an example, the wireless device may determine that the first symbol of the uplink channel/signal is outside a time window, started from a last symbol of a CORESET that the wireless device detects the DCI, with the length of T_(proc,2). In an example, based on determining that the downlink signal/channel is a retransmission of the downlink data/packet, the first symbol of the uplink channel/signal is occurred outside the time window, and the downlink data/packet is successfully decoded, the wireless device may drop/cancel the downlink signal/channel in the at least one symbol of the slot. In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the uplink channel/signal in the slot.

In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the actual repetition of the uplink channel/signal, based on the repletion of the uplink channel/signal being scheduled by the higher layers, in the slot. By transmitting the actual repetition of the uplink channel/signal, the wireless device may improve the uplink data transmission latency.

FIG. 30 shows an example embodiment of a wireless device without partialCancellation capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure. The wireless device may receive the one or more configuration parameters. As shown in FIG. 30 , the wireless device may receive the DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) from the base station. In an example, the wireless device may determine that the first symbol of the uplink channel/signal is outside a time window, started from a last symbol of a CORESET that the wireless device detects the DCI, with the length of T_(proc,2). As shown in FIG. 30 , based on determining that the downlink signal/channel is a retransmission of the downlink data/packet, the first symbol of the uplink channel/signal is outside the time window, and the downlink data/packet is successfully decoded, the wireless device may drop/cancel the downlink signal/channel in the at least one symbol of the slot. In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the uplink channel/signal in the slot.

In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the actual repetition of the uplink channel/signal, based on the repletion of the uplink channel/signal being scheduled by the higher layers, in the slot. By transmitting the actual repetition of the uplink channel/signal, the wireless device may improve the uplink data transmission latency.

FIG. 31 shows an example embodiment of a wireless device capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure. The wireless device may receive the one or more configuration parameters. As shown in FIG. 31 , the wireless device may receive the DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) from the base station. In an example, the higher layers (e.g., the MAC layer) of the wireless device may indicate a transmission of an SRS in the slot, colliding/overlapping with the downlink signal/channel in at least one symbol of the slot. As shown in FIG. 31 , the wireless device may determine that the first symbol of the SRS transmission is within a time window, started from a last symbol of a CORESET that the wireless device detects the DCI, with the length of T_(proc,2).

As shown in FIG. 31 , based on determining that the downlink signal/channel is a retransmission of the downlink data/packet, the first symbol of the SRS transmission is within the time window, and the downlink data/packet is successfully decoded, the wireless device may drop/cancel the downlink signal/channel in the at least one symbol of the slot. In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the SRS in the slot.

FIG. 32 shows an example embodiment of a wireless device capability communicating with an NTN base station, in accordance with certain aspects of the present disclosure. The wireless device may receive the one or more configuration parameters. As shown in FIG. 32 , the wireless device may receive the DCI from the base station. In an example, the wireless device may determine that the first symbol of the SRS transmission is outside a time window, started from a last symbol of a CORESET that the wireless device detects the DCI, with the length of T_(proc,2). In an example, based on determining that the downlink signal/channel is a retransmission of the downlink data/packet, the first symbol of the SRS transmission is outside the time window, and the downlink data/packet is successfully decoded, the wireless device may drop/cancel the downlink signal/channel in the at least one symbol of the slot. In an example, by dropping/canceling the downlink signal/channel in the at least one symbol of the slot, the wireless device may perform transmitting the SRS in the slot.

FIG. 33 shows an example embodiment of a wireless device communicating with an NTN base station, in accordance with certain aspects of the present disclosure. The wireless device may receive the one or more configuration parameters. As shown in FIG. 33 , the wireless device may receive the DCI from the base station. In an example, the higher layers (e.g., the MAC layer) of the wireless device may indicate a transmission of an uplink channel/signal (e.g., PUSCH, PRACH, PUCCH, or SRS) in the slot, colliding/overlapping with the downlink signal/channel in at least one symbol of the slot. In an example, the higher layers may indicate a repetition of the uplink channel/signal (e.g., PUSCH or PUCCH) in the slot.

In an example, based on determining that the downlink signal/channel is a retransmission of the downlink data/packet (e.g., NDI bit is not toggled), and the downlink data/packet is successfully decoded, the wireless device may drop/ignore the DCI. By dropping/ignoring the DCI, the physical layer of the wireless device may not indicate the downlink signal/channel to the higher layers (e.g., MAC layer). In an example, by dropping/ignoring the DCI, the wireless device may perform transmitting the uplink channel/signal in the slot. By transmitting the uplink channel/signal, the wireless device may improve the uplink data transmission latency.

In an example, by dropping/ignoring the DCI, the wireless device may perform transmitting the actual repetition of the uplink channel/signal, based on the repletion of the uplink channel/signal being scheduled by the higher layers, in the slot. By transmitting the actual repetition of the uplink channel/signal, the wireless device may improve the uplink data transmission latency.

A base station (e.g., an NTN base station) may transmit one or more configuration parameters to a wireless device. The one or more configuration parameters may indicate that a HARQ process i is feedback disabled. The base station may transmit a DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1), to the wireless device, indicating a downlink channel/signal (e.g., PDSCH or CSI-RS) associated with the HARQ process i carrying a downlink packet/data (comprising one or more transport blocks (TBs)) in a slot. In an example, the downlink signal/channel may be a (blind) retransmission of the downlink packet. The base station may transmit at least one previous (re)transmission of the downlink packet. The base station may schedule the downlink channel/signal without requiring receiving one or more HARQ-ACK/NACK information bits associated with the at least one previous (re)transmission from the wireless device. In an example, the downlink channel/signal may collide/overlap with an uplink channel/signal (e.g., PUSCH, PRACH, PUCCH) in the slot in at least one symbol. The higher layers (e.g., the MAC layer) of the wireless device may indicate the uplink channel/signal. In an example, the downlink channel/signal may collide/overlap with a repetition of the uplink channel/signal (e.g., PUSCH or PUCCH) in the slot in the at least one symbol.

In an example, based on determining that the downlink signal/channel is a retransmission of the downlink data/packet (e.g., NDI bit is not toggled), the base station may monitor for receiving the uplink channel/data from the wireless device in the slot.

According to an example embodiment, the wireless device may receive, from a base station, a first transmission of a downlink packet. The wireless device may receive downlink control information (DCI) comprising a downlink assignment of a second transmission of the downlink packet. The wireless device may determine that the second transmission overlaps with at least one symbol of a third transmission. The wireless device may dropping/canceling, during the at least one symbol, the second transmission based on successfully decoding the downlink packet via the first transmission and a feedback of the first transmission being disabled.

In an example, the wireless device may perform the third transmission.

In an example, the first transmission may be physical downlink shared channel (PDSCH) and the second transmission is PDSCH.

In an example, the first transmission channel may be state information reference signal (CSI-RS) and the second transmission is CSI-RS.

In an example, the third transmission may be indicated by the medium access control (MAC) layer of the wireless device.

In an example, the third transmission may be indicated by the radio resource control (RRC) layer of the wireless device.

In an example, the wireless device may support a partial cancellation capability.

In an example, the wireless device may not support a partial cancellation capability.

In an example, the wireless device may determine that the third transmission is at least one of physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or physical random access channel (PRACH). The wireless device may determine that the first symbol of the third transmission is within a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected. The wireless device may indicate the partial cancellation capability.

In an example, the wireless device may determine that the third transmission is at least one of: physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or physical random access channel (PRACH). The wireless device may determine that the first symbol of the third transmission is outside a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected. The wireless device may indicate the partial cancellation capability.

In an example, the wireless device may determine that the third transmission is at least one of: physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or physical random access channel (PRACH). The wireless device may determine that the first symbol of the third transmission is outside a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected. The wireless device may not support the partial cancellation capability.

In an example, the wireless device may determine that the third transmission is sounding reference signal (SRS) and the first symbol of the third transmission is within a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected.

In an example, the wireless device may determine that the third transmission is sounding reference signal (SRS) and the first symbol of the third transmission is outside a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected.

In an example, a first symbol of the second transmission may be occurred with a preconfigured gap from a last symbol of the first transmission.

In an example, the first transmission may correspond with a first hybrid automatic repeat request (HARQ) process that is feedback disabled and the second transmission is corresponding with the first HARQ process.

In an example, wherein the base station is a non-terrestrial network (NTN) base station.

According to an example embodiment, the wireless device may receive, from a base station, a first transmission of a downlink packet. The wireless device may receive a downlink control information (DCI) comprising a downlink assignment of a second transmission of the downlink packet. The wireless device may determine that the second transmission is overlapped with at least one symbol of a third transmission. The wireless device may perform, during the at least one symbol, the second transmission based on successfully decoding the downlink packet via the first transmission and a feedback of the first transmission being disabled.

In an example, the wireless device may drop/cancel the second transmission during the at least one symbol.

In an example, the first transmission may be physical downlink shared channel (PDSCH) and the second transmission is PDSCH.

In an example, the first transmission channel may be state information reference signal (CSI-RS) and the second transmission is CSI-RS.

In an example, the third transmission may be indicated by the medium access control (MAC) layer of the wireless device.

In an example, the third transmission may be indicated by the radio resource control (RRC) layer of the wireless device.

In an example, the wireless device may support a partial cancellation capability.

In an example, the wireless device may not support a partial cancellation capability.

In an example, the wireless device may determine that the third transmission is at least one of physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or physical random access channel (PRACH). The wireless device may determine that the first symbol of the third transmission is within a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected. The wireless device may indicate the partial cancellation capability.

In an example, the wireless device may determine that the third transmission is at least one of: physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or physical random access channel (PRACH). The wireless device may determine that the first symbol of the third transmission is outside a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected. The wireless device may indicate the partial cancellation capability.

In an example, the wireless device may determine that the third transmission is at least one of: physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or physical random access channel (PRACH). The wireless device may determine that the first symbol of the third transmission is outside a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected. The wireless device may not support the partial cancellation capability.

In an example, the wireless device may determine that the third transmission is sounding reference signal (SRS) and the first symbol of the third transmission is within a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected.

In an example, the wireless device may determine that the third transmission is sounding reference signal (SRS) and the first symbol of the third transmission is outside a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected.

In an example, a first symbol of the second transmission may be occurred with a preconfigured gap from a last symbol of the first transmission.

In an example, the first transmission may correspond with a first hybrid automatic repeat request (HARQ) process that is feedback disabled and the second transmission is corresponding with the first HARQ process.

In an example, wherein the base station is a non-terrestrial network (NTN) base station.

According to an example embodiment, the wireless device may receive, from a base station, a first transmission of a downlink packet. The wireless device may receive a downlink control information (DCI) comprising a downlink assignment of a second transmission of the downlink packet. The wireless device may determine that the second transmission is overlapped with at least one symbol of a third transmission. The wireless device may ignore/drop/cancel the downlink assignment based on successfully decoding the downlink packet via the first transmission and a feedback of the first transmission being disabled.

In an example, the wireless device may perform the third transmission.

In an example, the first transmission may be physical downlink shared channel (PDSCH) and the second transmission is PDSCH.

In an example, the first transmission channel may be state information reference signal (CSI-RS) and the second transmission is CSI-RS.

In an example, the third transmission may be indicated by the medium access control (MAC) layer of the wireless device.

In an example, the third transmission may be indicated by the radio resource control (RRC) layer of the wireless device.

In an example, the wireless device may support a partial cancellation capability.

In an example, the wireless device may not support a partial cancellation capability.

In an example, the wireless device may determine that the third transmission is at least one of physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or physical random access channel (PRACH). The wireless device may determine that the first symbol of the third transmission is within a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected. The wireless device may indicate the partial cancellation capability.

In an example, the wireless device may determine that the third transmission is at least one of: physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or physical random access channel (PRACH). The wireless device may determine that the first symbol of the third transmission is outside a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected. The wireless device may indicate the partial cancellation capability.

In an example, the wireless device may determine that the third transmission is at least one of: physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or physical random access channel (PRACH). The wireless device may determine that the first symbol of the third transmission is outside a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected. The wireless device may not support the partial cancellation capability.

In an example, the wireless device may determine that the third transmission is sounding reference signal (SRS) and the first symbol of the third transmission is within a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected.

In an example, the wireless device may determine that the third transmission is sounding reference signal (SRS) and the first symbol of the third transmission is outside a window with a predetermined length started from a last symbol of a control resource set (coreset) that the DCI is detected.

In an example, a first symbol of the second transmission may be occurred with a preconfigured gap from a last symbol of the first transmission.

In an example, the first transmission may correspond with a first hybrid automatic repeat request (HARQ) process that is feedback disabled and the second transmission is corresponding with the first HARQ process.

In an example, wherein the base station is a non-terrestrial network (NTN) base station.

According to an example embodiment, a base station may transmit, to a wireless device, a first transmission of a downlink packet. The base station may transmit downlink control information (DCI) comprising a downlink assignment of a second transmission of the downlink packet. The base station may determine that the second transmission overlaps with at least one symbol of a third transmission. The base station may receive the third transmission based on a feedback of the first transmission being disabled. 

1. A method comprising: receiving, by a wireless device, a first downlink control information (DCI): scheduling a reception of a transport block; and indicating a hybrid automatic request (HARQ) process number with feedback disabled; receiving a second DCI: scheduling a retransmission of the transport block; and indicating the HARQ process number with feedback disabled, wherein the retransmission of the transport block overlaps in time with at least one symbol of a transmission of an uplink signal; and based on successfully decoding the transport block scheduled by the first DCI: dropping the retransmission of the transport block scheduled by the second DCI; and transmitting the uplink signal.
 2. The method of claim 1, wherein the transmission of the uplink signal is indicated by a medium access control (MAC) layer of the wireless device or a radio resource control (RRC) layer of the wireless device.
 3. The method of claim 1, wherein the uplink signal is at least one of: a physical uplink shared channel (PUSCH) transmission; a physical uplink control channel (PUCCH) transmission; a physical random access channel (PRACH) transmission, or a sounding reference signal (SRS).
 4. The method of claim 1, wherein a starting symbol of the uplink signal is within a window with a predetermined length started from a last symbol of a control resource set (coreset) that the second DCI is detected.
 5. The method of claim 4, wherein the predetermined length is based on a processing time of a physical uplink channel.
 6. The method of claim 1, wherein the wireless device communicates with a base station via a non-terrestrial network (NTN).
 7. The method of claim 1, wherein the wireless device supports a partial cancellation capability.
 8. The method of claim 1, wherein the wireless device does not support a partial cancellation capability.
 9. The method of claim 1, further comprising determining the transport block being successfully decoded prior to at least one of transmitting the uplink signal or receiving the second DCI.
 10. The method of claim 1, further comprising skipping transmitting a HARQ acknowledgement indicating decoding result of the transport block.
 11. A wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: receiving, by a wireless device, a first downlink control information (DCI): schedule a reception of a transport block; and indicate a hybrid automatic request (HARQ) process number with feedback disabled; receiving a second DCI: schedule a retransmission of the transport block; and indicate the HARQ process number with feedback disabled, wherein the retransmission of the transport block overlaps in time with at least one symbol of a transmission of an uplink signal; and based on successfully decoding the transport block scheduled by the first DCI: drop the retransmission of the transport block scheduled by the second DCI; and transmit the uplink signal.
 12. The wireless device of claim 11, wherein the transmission of the uplink signal is indicated by a medium access control (MAC) layer of the wireless device or a radio resource control (RRC) layer of the wireless device.
 13. The wireless device of claim 11, wherein the uplink signal is at least one of: a physical uplink shared channel (PUSCH) transmission; a physical uplink control channel (PUCCH) transmission; a physical random access channel (PRACH) transmission, or a sounding reference signal (SRS).
 14. The wireless device of claim 11, wherein: a starting symbol of the uplink signal is within a window with a predetermined length started from a last symbol of a control resource set (coreset) that the second DCI is detected; and the predetermined length is based on a processing time of a physical uplink channel.
 15. The wireless device of claim 11, wherein the wireless device communicates with a base station via a non-terrestrial network (NTN).
 16. The wireless device of claim 11, wherein the wireless device supports a partial cancellation capability.
 17. The wireless device of claim 11, wherein the wireless device does not support a partial cancellation capability.
 18. The wireless device of claim 11, further comprising determining the transport block being successfully decoded prior to at least one of transmitting the uplink signal or receiving the second DCI.
 19. The wireless device of claim 11, further comprising skipping transmitting a HARQ acknowledgement indicating decoding result of the transport block.
 20. A system comprising: a wireless device comprising one or more first processors and memory storing instructions that, when executed by the one or more first processors, cause the wireless device to: receiving a first downlink control information (DCI): schedule a reception of a transport block; and indicate a hybrid automatic request (HARQ) process number with feedback disabled; receiving a second DCI: schedule a retransmission of the transport block; and indicate the HARQ process number with feedback disabled, wherein the retransmission of the transport block overlaps in time with at least one symbol of a transmission of an uplink signal; and based on successfully decoding the transport block scheduled by the first DCI: drop the retransmission of the transport block scheduled by the second DCI; and transmit the uplink signal; and a base station comprising one or more second processors and memory storing instructions that, when executed by the one or more second processors, cause the base station to: receive the uplink signal. 